feat: replace StudioFooter with StudioFooterSlot

[Anas12091101]

Description

This PR replaces StudioFooter with StudioFooterSlot, allowing the customization of footer in the authoring MFE. StudioFooterSlot is added to frontend-slot-footer in this PR: openedx-unsupported/frontend-slot-footer#60

Useful information to include:

• Which edX user roles will this change impact? Common user roles are "Learner", "Course Author",
  "Developer", and "Operator".
• Include screenshots for changes to the UI (ideally, both "before" and "after" screenshots, if applicable).
• Provide links to the description of corresponding configuration changes. Remember to correctly annotate these
  changes.

Supporting information

Slack Thread: https://openedx.slack.com/archives/C04BM6YC7A6/p1741354164744729?thread_ts=1741187643.034179&cid=C04BM6YC7A6
Issue: https://github.com/mitodl/hq/issues/5689

Testing instructions

• Checkout to this branch and run npm ci.
• Verify that the default studio footer loads perfectly without any issues.
• Create env.config.jsx file and add the following:

import { DIRECT_PLUGIN, PLUGIN_OPERATIONS } from '@openedx/frontend-plugin-framework';

const config = {
  pluginSlots: {
    studio_footer_slot: {
      plugins: [
        {
          // Hide the default footer
          op: PLUGIN_OPERATIONS.Hide,
          widgetId: 'default_contents',
        },
        {
          // Insert a custom footer
          op: PLUGIN_OPERATIONS.Insert,
          widget: {
            id: 'custom_footer',
            type: DIRECT_PLUGIN,
            RenderWidget: () => (
              <h1 style={{textAlign: 'center'}}>🦶</h1>
            ),
          },
        },
      ]
    }
  },
}

export default config;

Open the MFE in your browser and verify that the studio footer is replaced with 🦶 on all pages where it is present.

Other information

Include anything else that will help reviewers and consumers understand the change.

• Does this change depend on other changes elsewhere?
  This PR depends on feat: add studio footer slot openedx-unsupported/frontend-slot-footer#60. First feat: add studio footer slot openedx-unsupported/frontend-slot-footer#60 needs to be merged and released and then this PR should be updated to the new version of @openedx/frontend-slot-footer before merge.

[openedx-webhooks]

Thanks for the pull request, @Anas12091101!

This repository is currently maintained by @openedx/2u-tnl.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[asadali145]

looks good. Will approve after the final updates.

[asadali145]

Suggested change

	footer_slot: {
	studio_footer_slot: {

[asadali145]

Suggested change

	# Footer Slot
	# Studio Footer Slot

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.53%. Comparing base (15fcb55) to head (0222e61).
Report is 17 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1729      +/-   ##
==========================================
+ Coverage   93.46%   93.53%   +0.07%     
==========================================
  Files        1124     1132       +8     
  Lines       22746    23043     +297     
  Branches     4823     4978     +155     
==========================================
+ Hits        21259    21553     +294     
+ Misses       1419     1414       -5     
- Partials       68       76       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Anas12091101]

@brian-smith-tcril could you please review this PR?

[Anas12091101]

Hi @brian-smith-tcril, I wanted to check in on this PR as we’re hoping to get it merged soon. Would you be able to take a look when possible? Happy to address any concerns.

[brian-smith-tcril]

I'd like to keep this dependency in here. frontend-slot-footer has an unversioned peer dependency on frontend-component-footer, so keeping a versioned dependency in here is helpful.