CEXT-6318: Create a separate package for Admin UI SDK

[oshmyheliuk]

Description

This PR is a part of #426. As ACL will need a rework based on the new structure, the new package for the admin ui can be delivered separately.

https://jira.corp.adobe.com/browse/CEXT-6318

Motivation and Context

To align with other packages for eventing/webhook, the admin ui API should also be extracted to a separate package.

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have read the DEVELOPMENT document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[changeset-bot]

🦋 Changeset detected

Latest commit: 6cc7292

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages

Name	Type
@adobe/aio-commerce-lib-app	Patch
@adobe/aio-commerce-sdk	Minor
@adobe/aio-commerce-lib-admin-ui	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[obarcelonap]

Overall LGTM, please review the publication config in package.json and the snake case in registering extension payload.

[obarcelonap]

You can just await the deletion without this then block

await httpClient.delete(
  `adminuisdk/extension/${workspaceName}/${extensionName}`,
  fetchOptions,
);

[iivvaannxx]

@obarcelonap It depends, actually. For example, we did this with the event subscriptions endpoint, and for some reason, it always returned [] (not sure if it was a Commerce API thing specific to that endpoint). That's why I suggested to him to use .then without a return value to force void and ensure it even if the API changes.

[obarcelonap]

I proposed to await without returning so you still get Promise<Void> as return type. In any case not a blocker.

[iivvaannxx]

I see, I didn't understand. Works both ways, I don't have a strong opinion.

[iivvaannxx]

It was already in camelCase in the current implementation, and it seems to work in both formats for the AdminUI SDK API. But yes, probably it's better to change to the documentation format

So I just remembered that @capape explained a related issue to me just yesterday, and asked him what the reason might be. Turns out Commerce converts everything to camelCase before deserialization, that's why it seems to work anyway. You could say it's not a bug, but a feature 🤣

FYI @obarcelonap @oshmyheliuk

@capape Correct me if I understood wrong 🙈