Issue Summary:

Dynamic Forge modules registered via POST /forge/installation/v2/dynamic/module do not receive the context.license property when view.getContext() is called from a Custom UI. The license property is returned as null instead of containing the actual license status.

Steps to Reproduce

• Register a dynamic Forge module of type jira:issueContext using the Forge Dynamic Modules API:

const moduleConfig = {
  type: 'jira:issueContext',
  data: {
    title: 'Summary Panel',
    label: 'Summary Panel',
    resource: 'appResource',
    resolver: {
      function: 'resolver',
    },
  },
};

const postRequest = await asApp().requestAtlassian(
  route`/forge/installation/v2/dynamic/module/`,
  {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
    },
    body: JSON.stringify(moduleConfig),
  },
); 

• In the Custom UI of the dynamically registered module, call view.getContext() from @forge/bridge and inspect the license property:

import { view } from '@forge/bridge';

const context = await view.getContext();
console.log(context.license); // Returns null 

Expected Results

The context.license property should be populated with the actual license status of the app for the given installation, consistent with the behavior of statically defined modules.

Actual Results

The context.license property is returned as null when view.getContext() is called from a Custom UI within a dynamically registered Forge module. No exception is thrown — the value is simply missing.

Workaround

Required, if there is no workaround please state:
Currently there is no known workaround for this behavior. A workaround will be added here when available