Issue Summary:

If using Forge rolling releases to upgrading installations from a version without `rovo:agent` modules to a version with these modules, there is a bug where new modules are not discoverable until the admin accepts new permissions to upgrade to latest permission version.

Steps to Reproduce

1. Have an app that has opted-in to use decoupled permissions
2. Deploy a new version with both permission changes and additional `rovo:agent` modules.

Expected Results

Installations with outdated permissions should still be able to access the new agent.

Actual Results

Installations with outdated permissions do not discover the agent, until they upgrade permissions.

Workaround

Back-port the new `rovo:agent` to all previous major versions that installations were upgraded from.

NOTE: You can find the version numbers by running forge version bulk-upgrade create and note which major versions have installations.