Fix miscellaneous oddities around the class reference (part 5)

[Mickeon]

Continuation of #105073

This PR addressed yet yet another huge chunk of class reference oddities I remembered to note down for later while localizing the class reference. Some of these are clear typos, some are inconsistencies, some are just awkward.

Of particular note:

• Link to the existing constants in CameraFeed's set_format
• Modify some descriptions of EditorExportPlatformExtension and ReferenceRect for clarity
• Modify some descriptions of Animation, EditorExportPreset, MeshDataTool, PointMesh, and LookAtModifier3D substantially
• Removed navigation's "(as 2D uses the 3D server behind the scene)."
  • It should be incorrect now. CC @smix8 @AThousandShips
• Be more explicit in some some navigation server methods, instead of "e.g."
  • See Rocketchat discussion
• Removed a formula in plain text in ResourceImporterImageFont
  • We should genuinely avoid expressions like "columns * rows", especially for simple formulas. It's hard to parse
• Link to the documentation in ProjectSetting's shadow atlas descriptions
  • That is, instead of vaguely saying so with "see the documentation"
  • The reworded descriptions are partially taken from Viewport's corresponding properties
• Elaborate more on what "lacunarity" is in FastNoiseLite's domain_warp_fractal_lacunarity.
  • This term is so niche most languages genuinely don't have a term for it
• Standardize the examples in RegEx's class
• Replace x with × character in more places
• Replace a few occurrences (often the only ones) of "comprise", "constitute", "multi-channel", "resemble", "comma-delimited", "post process", "pre process", "made up", "is slated" with more common alternatives
• Fixed occurrences of "Compatibility renderer" being in lowercase
• Fixed an occurrence of COLLADA not being fully capitalized
• Fixed "parameters" being referred as "arguments" in a few places
• Fixed some missing articles on the way

For some of the descriptions affected, additional tweaks have been made to justify a whole translation string change.

[Mickeon]

Yes, that's right. The enum for it is exposed perfectly fine, but it's not used by this method.

• Use ScriptExportMode enum in EditorExportPreset #107167

[Mickeon]

I was genuinely just considering listing all of the valid classes, because summarising them as "action events" is a really bad way to put it.
Not only is "action event" not something consistently used in the docs to refer to this concept, but it can easily be misunderstood for InputEventAction (as it literally happens in this line)

[Mickeon]

I am genuinely not sure why this is noted here and not in transition_type itself. I also don't quite understand what the last sentence is trying to say.

[AThousandShips]

LGTM

[akien-mga]

Thanks!