AEP Web SDK Configuration View - Data Element :: XDM Object requires AEP Schema Registry Permissions

### Expected Behaviour
When rendering the "AEP Web SDK" Configuration View - Data Element :: XDM Object, there are API calls to pull in schema information. If the Launch user doe not have the appropriate permissions for these API calls, the extension view fails to render. At a minimum, the API response code should be caught and a message indicating the required permissions should be displayed.

### Actual Behaviour
If the Launch user doe not have the appropriate permissions to get AEP Schema info, the extension view fails to render.

### Reproduce Scenario (including but not limited to)
Find two users with access to Adobe Experience Platform Launch Data Collection, by Adobe.
Assure that one user has access to view AEP Schemas
Assure that the other user does not have access to view AEP Schemas

Have the first user create an AEP Web SDK :: XDM Object Data Element (selecting Sandbox and Schema).
Have the second user attempt to edit that data element.
Boom.

IDK what happens if both users have AEP schema access but different sandbox access. I would assume that a similarly bvad situation exists.

#### Steps to Reproduce
See above.

#### Platform and Version
Adobe Experience Platform Launch Data Collection, by Adobe.

#### Sample Code that illustrates the problem

#### Logs taken while reproducing problem

Start by reproducing the failure in the AEP Web SDK Configuration View for the Data Element :: XDM Object with a user who lacks AEP Schema Registry permissions, then inspect the schema API calls made while selecting the sandbox and schema. Done means the view no longer fails to render and displays a message describing the required permissions when those calls return an error.

Written by the indexing model from the issue text.