Fix action registration order to occur after extensions are loaded.
Review Request #13625 — Created March 9, 2024 and submitted — Latest diff uploaded
The new actions support attempted to register actions before extensions
were loaded, preventing JavaScript-side extensions from being able to
register automatically.This moves actions setup to after JavaScript extension initialization,
placing it in the same order as other registrations.
Tested an action in an extension and verified that it could be
registered correctly.This was noticed with RBCommons.