Edit prompt template from studio

[felipemontoya]

This PR adds a basic UI for looking at the configured Profiles and their templates from studio.

This first UI allows users to look at the profile at the scope and should these user templates be able to edit the template. Users that have "admin" course team permissions will be able to read the profile and scope in the studio UI and be able to write to the prompt template.

When saving, if a template is used in more than one profile, users are warned but allowed to continue if they so choose.

These images show how the UI looks:

[openedx-webhooks]

Thanks for the pull request, @felipemontoya!

This repository is currently maintained by @felipemontoya.

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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.22%. Comparing base (972f2fe) to head (c754525).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #183      +/-   ##
==========================================
+ Coverage   95.13%   95.22%   +0.09%     
==========================================
  Files          67       68       +1     
  Lines        7322     7901     +579     
  Branches      387      414      +27     
==========================================
+ Hits         6966     7524     +558     
- Misses        267      286      +19     
- Partials       89       91       +2     

Flag	Coverage Δ
unittests	95.22% <ø> (+0.09%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.

[Pavilion4ik]

Hi @felipemontoya ,

I noticed that during the AI Extensions Monthly Working Group yesterday you discussed an idea similar to what I was planning to introduce in this task.

Since you’re already working on it, I decided not to duplicate the effort. Instead, I’ve created a patch file that might be useful for you - feel free to take a look when you have time.

course_author_ai_settings_proposal.md
course_author_ai_settings.patch

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Pull request overview

Copilot reviewed 12 out of 12 changed files in this pull request and generated 11 comments.

[felipemontoya]

@Henrrypg I think this is worth a human review now. I fixed the permission model so they work in ulmo/teak.

[Henrrypg]

Just ask to remove some inlines, It is working fine in dev and the code looks very good, thanks @felipemontoya