Following up to D15615, I noticed that many messages are either
properly extracted, but not translated due to the use of printf-style
formatting in strings, or not extracted at all. Using the pgettext
function explicitly before formatting fixes that.

Since the affected messages are already extracted, no additional work
is needed from translators.

Reviewed By: mont29

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

Introduce a method to annotate types and names of entries in the
`bones` container of rig components and apply it, and other type
annotations, to a number of not very complex rig classes.

- Introduce BaseRigMixin as a typed base class for mixins intended
  for use in rig classes (using BaseRig as a parent causes issues).
- Introduce TypedBoneDict that does not suppress the unknown attribute
  analysis in PyCharm, and use it in a system of subclasses to
  annotate the bones in various rigs. BaseBoneDict is necessary
  because the annotation affects all subclasses, so TypedBoneDict
  cannot inherit from BoneDict with the annotation.
- Add or adjust other type annotations of rig methods and utilities.
- Fix other warnings, e.g. undeclared attributes, excessively long
  lines, whitespace style issues and typos.

Refactor the matrix stack in a way that does not require matrix
inversion. Basically, store the state of the final transform in
the stack.

Technically this makes regression test to fail with Blender Icons,
but the new code gives more correct icons. So the reference image
is to simply be regenerated.

Added the Asset Browser, Spreadsheet  and Geometry Node editors in their respective categories for pie menu add-on.

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

Unfortunately, messages cannot be properly extracted from f-strings.
Use format() method instead.

Reviewed By: Sybren A. Stüvel, Campbell Barton

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

Unfortunately, messages cannot be properly extracted from f-strings.
Use format() method instead.

Reviewed By: Sybren A. Stüvel, Campbell Barton

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

CloudRig has a feature that allows the user to automatically generate
Action constraints that move bones of the rig based on the position
of other bones. This is done by adding and configuring the actions
in a UI panel of the metarig. The feature also supports corrective
actions that activate based on the state of two other actions.

This ports the feature to base Rigify with the necessary changes in
code organization and style, and replacing CloudRig-specific code.

There are also some functional changes:

- The order of action constraints is reversed.
- The way symmetry of LOCATION_X is handed is changed to
  match how Paste Pose Flipped works.
- The action slot UI is shown even without a generated rig.
- More alerts in the UI, e.g. for duplicate rows.

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

Also declare stage names for auto-completion.

- Remove time offset -- this feature was removed in Blender 2.61
- Cleanup Code
- Rename groups to collections
- Rename dupli to instancing
- Remove BGE feature
- Remove non existent `MESH_MT_CopyImagesFromLayer`
- Update operator labels

Addresses parts of T100240

D16212: Curve Tools: Ensure nested paths in exported SVG look as expected. (Authored by Johan Althoff (teetow))

- The first imported one is now set as the rendered one
- Color Attribute Node does no more specify the layer, so rendered one is used

When we enable the Rigify add-on with installed feature sets, we were
trying to register those feature sets as well, but failing because the
feature set list wasn't populated yet; It would ALWAYS be an empty list.

Moving refresh() inside get_enabled_modules_names() might be better.

Caused by D15961, which changed the behavior of `dpi` and
`pixel_size`.

Instead of using a single value for `dpifac` (renamed to `dpi_fac`),
use a value depending on whether we want pixel density or line
width.

This patch has the side-effect that the line width from the user
preferences is now respected. It seems more logical that way, but I
can't test with a hi-dpi display to see how that looks.

If we want to get the old behavior back, we can just get rid of
`prefs_line_width()` and replace its calls with `dpi_fac()`.

A similar issue was also fixed for Icon Viewer.

Change the global poll function to check that the node tree is not
from a library, disabling most Node Wrangler operators.

This fixes the issue, not only for material nodes as in the original
report, but also on compositing node trees from linked scenes and
geometry nodes.

The `scene.render.fps` setting must be an integer nowadays. Instead of
storing a `float` there, the rounded FPS is stored as integer, and the
`fps_base` property is used to scale this to the desired frame rate.

Contributed by luzpaz.

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

Don't change current point coordinate for implicit path close.
This can fix some broken paths in T92713.

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

As part of a change years ago[1], the addon location was moved from the
`Add->Mesh` menu to the `Add->Image` menu but the "location" field was
never updated.  The manual is already correct.

[1] 07b8375e

As suggested by Omar Emara (@OmarSquircleArt), break after first
matching framerate found, instead of searching the whole list everytime,
ending up selecting the last matching value.

NTSC 'drop frame' type are rather unusual, they should never be
auto-selected anyway.

This can fix some broken paths in T92713, like the following PeerTube icon.

| before | now
| {F13615071} | {F13615072}

But some icons are still incomplete due to other issues.

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