Only mesh add headings for attributes to key; now curves, surfaces and
lattices do, too.

They were lost in a rebase, somewhere.

- key_points -> key_point_location
- key_shape -> key_shape_key
- key_vgroups -> key_vertex_group
- key_ebevel -> key_edge_bevel
- key_vbevel -> key_vertex_bevel

Vertex color access through `Mesh.vertex_colors` is deprecated and
will be removed eventually.
https://wiki.blender.org/wiki/Reference/Release_Notes/3.2/Python_API#Deprecation

It is already not entirely functional for AnimAll's workflow: if there
are multiple vertex color layers, the active one cannot be selected
because the interface is no longer exposed. This results in the user
being unable to select which layer they want to animate.

Besides, all functionality is covered by the more generic attributes
system. An operator is provided to upgrade animation curves still
using the old system.

Vertex colors have been replaced by a more generic attribute system,
so we need to support that.

This allows animating not only color attributes, but also other types.
Not sure that's very useful as most attributes can't be manually
edited as far as I understand, but it *is* now possible!

The remote version didnt have the GPL Header in its full form before.
So restoring this part to the original state.

In the prior versions of this addon I had to generate a list of builtin and standard python modules,
which need to be excluded in the walk function.

This function is being called recursively over all blender py modules
and addon modules.

Certain builtin or standard modules of python seem to have some recursion in their module structure,
which needs to be avoided.

Since Python 3.10, you can use 'sys.stdlib_module_names' for a basic list.
Possibly the old method generated an incomplete list.

Highly suspect the source FBX file to be broken, but investigating a 20MB
binary FBX file is not really an option right now, so cannot be 100%
sure. This can only be realistically investigated if we get a much
smaller reproducible case.

In the mean while, add similar check about indices validity for source
FBX data as we already have for destination Blender data arrays. This
allows to keep importing instead of 'crshing' the import process at
least.

Add missing values to the `FBX_FRAMERATES` data, including those that
Blender does not really support (the NTSC 'drop frames' variants, better
to have them mapped to regular NTSC framerate than completely ignored).

When using the node.nw_link_out operator (O key) in a world node tree,
a material output would be created instead of a world one.

This implements the use of shortcut `O` to connect the first geometry
output of the active node, to the group output.

Right now, only geometry is concerned, and the operator is cancelled
if another output type is found, such as an `int`.

When creating an armature containing a camera, without the add-on, the
UI panel tries to display, but the data is not set up to use it
properly.

This update brings the following changes:

- updated snow material (it was assigning values to wrong sockets in Principled node)
- converted Color Ramp nodes to Map Range
- changed tracker URL

Differential Revision: https://developer.blender.org/D15148

This is no longer necessary, see: T98554.

Update by @TheRedWaxPolice in T74360.