feat: extend the account fields with the already existing extended_profile_fields

[bra-i-am]

Description

This PR aims to allow the extension of the default account fields by using the extended_profile_fields feature with a custom form app like the example

Main changes

• src/account-settings/ExtendedProfileField.jsx: New component to manage the fields added to the extended_profile_field settings attribute (it is only covered checkbox, text and select fields)
• src/account-settings/data/services.js: Add a service to retrieve all the extended profile field properties (these are added with the custom form app and retrieved to the MFE with the mfe_context API)

How Has This Been Tested?

1. Init a Sumac environment
2. Git clone and mount this MFE with tutor mounts add /path/to/cloned/mfe
3. Git clone this custom form app which counts with checkbox, select and text fields
4. Mount the custom form app with tutor mounts add lms:/path/to/cloned/custom-form-app:/openedx/extra-deps/custom-form-app and install it using tutor dev exec lms pip install -e ../extra-deps/custom-form-app
5. Add the following env variables

   # lms.env.yml
   ADDL_INSTALLED_APPS:
     - "custom_reg_form"
   ENABLE_COMBINED_LOGIN_REGISTRATION: true
   REGISTRATION_EXTENSION_FORM: "custom_reg_form.forms.ExtraInfoForm"
   
   # cms.env.yml
   ENABLE_COMBINED_LOGIN_REGISTRATION: true

6. Add the following settings to the Site Configurations > local.openedx.io:8000:

   {
         "ENABLE_PROFILE_MICROFRONTEND": "true",
   "ENABLE_DYNAMIC_REGISTRATION_FIELDS": "true",
   "MFE_CONFIG": {
       "ENABLE_DYNAMIC_REGISTRATION_FIELDS": "true"
   },
   "REGISTRATION_EXTRA_FIELDS": {
       "employment_situation": "required",
       "data_authorization": "required",
       "allow_newsletter": "required",
       "terms_of_service": "hidden",
       "honor_code": "hidden",
       "full_name": "required",
       "bio": "required",
       "wants_newsletter": "required",
       "favorite_language": "required",
       "password_hint": "required",
       "terms_accepted": "required"
   },
   "extended_profile_fields": [
       "data_authorization",
       "full_name",
       "bio",
       "wants_newsletter",
       "favorite_language",
       "password_hint",
       "terms_accepted"
   ],
   }

7. Run tutor dev restart
8. When you go to your account (Account MFE), you'll be able to interact with the extended fields added through the custom form app

Screenshots/sandbox (optional):

[openedx-webhooks]

Thanks for the pull request, @bra-i-am!

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

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.

---

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

Attention: Patch coverage is 74.19355% with 24 lines in your changes missing coverage. Please review.

Project coverage is 60.31%. Comparing base (92b7c58) to head (78d4b73).
Report is 21 commits behind head on master.

Files with missing lines	Patch %	Lines
src/account-settings/data/service.js	0.00%	6 Missing ⚠️
src/account-settings/AccountSettingsPage.jsx	16.66%	5 Missing ⚠️
src/account-settings/EditableCheckboxField.jsx	82.75%	5 Missing ⚠️
src/account-settings/data/reducers.js	0.00%	4 Missing and 1 partial ⚠️
src/account-settings/EditableField.jsx	78.57%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1193      +/-   ##
==========================================
+ Coverage   58.55%   60.31%   +1.76%     
==========================================
  Files         119      121       +2     
  Lines        2413     2505      +92     
  Branches      665      692      +27     
==========================================
+ Hits         1413     1511      +98     
+ Misses        934      931       -3     
+ Partials       66       63       -3     

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

[e0d]

@bra-i-am looks like this PR introduces some code coverage issues, can you please have a look?

[bra-i-am]

@e0d, I tried to cover all the code lines required to achieve the codecov check; there are some more warnings, but many are in lines so specific that I didn't get them with my changes.

Please let me know if covering the whole code is required or if having the codecov check is enough.

Thanks a lot! 🙏

[bra-i-am]

@awais-ansari @sundasnoreen12, I hope you are doing great!

I've been considering that this merge request might encounter issues during the merge due to the incorporation of a new feature. However, I also believe it would serve as a good recovery from the features lost in the transition to the MFEs (I planted this solution motivated by https://discuss.openedx.org/t/custom-fields-in-profile-form/6116/2, indeed).

In any case, I'm waiting for your comments to plan how I could proceed. Beforehand, thank you so much for your time!

[dcoa]

I not sure if this is necessary at the end is a wrapper, why not instead being a section in the account page (something like profile extra information or extension) or a subsection in the profile information section (as is shown in your implementation) that given the extended_profile information, render the corresponding fields?

[bra-i-am]

I made it only to avoid the component AccountSettingsPage from being bigger than it is at this moment. Additionally, maybe in the future we would add more field.type options, which could make the switch statement increase in size

Do you think it makes sense? :s

[dcoa]

I agree that the AccountSettingsPage, should not be larger, and if you are going to make this a slot extension I think having a section that group all the logic is better, what that means:

<AccountSettingsPage>
   ....
   <ExtendedProfile extendedData={extendedFilds}>
   ....
</AccountSettingsPage>

And then inside the component make the map, validate the data type and return the components needed

[bra-i-am]

@dcoa @awais-ansari @sundasnoreen12, I hope you are doing well

I'm closing this PR in favor of #1254, which creates a plugin slot to improve the handling of this

thanks ✨