refactor: update the app template for the console

[dcoa]

Description

This PR includes foundational updates and setup tasks to prepare the application for further development.

Changes Introduced

• Updated core libraries required for the application and delete all unnecessary ones.
• Updated the README.rst and related configuration files to reflect the latest setup and usage instructions.
• Created the authz/ folder as the starting point for the authorization MVP module development.

Notes

• The authz module is currently a placeholder and will be expanded in future PRs.
• I could not found a specific standard for the PORT definition so I use 2025 randomly but aiming for your guidance on it.

Additional information

• Decision for creation a new MFE feat(console): integrate AuthZ module and add the view tab frontend-app-authoring#2458 (comment)
• Console project information Confluence Administrative Console

[openedx-webhooks]

Thanks for the pull request, @dcoa!

This repository is currently maintained by @openedx/committers-frontend.

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.

[arbrandes]

Looks good overall, but I'm asking for a couple of changes.

[codecov]

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

[arbrandes]

Looks like my nits were addressed. Thanks!

[dcoa]

@arbrandes @sarina could you help me with the merge of this PR?

[arbrandes]

@dcoa, done!