Issue Summary

When using the new Version History UI and checking the content.type of a blog post in a Forge macro, the response is incorrect, showing "page" instead of "blogpost". 

Steps to Reproduce

1. Create a Forge app using the following module: 

   modules:   
    macro:     
       - key: content-type-bug-hello-world-macro
         resource: main
         render: native
         resolver:         
          function: resolver
         title: content-type-bug
         export:         
          function: resolver
     function:     
      - key: resolver
        handler: index.handler
   resources:   
     - key: main
       path: src/frontend/index.jsx 

2. Fetch the content type using this code for example:

   import { view } from '@forge/bridge';
   
   const context = await view.getContext();
   console.log(context.extension.content.type);
   

3. In the blogpost body, the macro will retrieve the correct content type:
   
4. Now go to Menu > Version History, it will show content.type as "page". Example in the Actual results session.

Expected Results

The type should match the actual content type, in this case "blogpost". As shown in the view mode, in the reproduction steps session.

Actual Results

Shows type "page":

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available