DEVDOCS-6249 - Content Refresh S2S Super Admin

[bc-terra]

DEVDOCS-6249

Reformatted file with reusable schemas.
Added new copy.
Added missing fields and parameters.
Adjusted responses to clarify structure.

What changed?

• Introduction presents relevant groundwork for Super Admins and the API.
• Endpoints now include clear summaries and descriptions.
• Request and response bodies are up-to-date, showing all available fields and parameters.
• YAML file is organized into several schema to reduce redundant text lines and improve efficiency for subsequent edits.

Release notes draft

• As part of our ongoing content refresh for B2B Edition developer documentation, we've fully refreshed the Server-to-Server Super Admin documentation. This includes
  • New, thorough descriptive copy
  • Explanation of complex error reporting
  • Inclusion of previously-missing fields for all endpoints

Anything else?

ping { @bc-Vince @CNanninga @BC-EEspinosa }

[bc-Vince]

Let me know if you need additional clarification on any of the questions in the comments.

[bc-Vince]

Is this field blank/null/etc if the Super Admin only has a storefront account and not a backend account?

[bc-terra]

From testing, whether/how uuid shows depends if it has a defined value. If the customer account doesn't have a UUID assigned, some endpoints will omit it. Endpoints that always show the UUID list it as an empty string, e.g. "uuid": "" in the response. Since BigCommerce customers usually don't have a UUID assigned by default, this is blank unless the merchant explicitly includes it.

[bc-Vince]

That might be worth calling out, since the field is included in at least one endpoint.

[bc-terra]

Suggested change

	description: "The UUID associated with the Super Admin's B2B Edition user account."
	description: |-
	An external ID associated with the Super Admin account. B2B Edition does not require UUID to be unique, despite the field's label. B2B Edition will not assign a UUID by default.
	> NOTE
	> Some endpoints will only return this field if it has a non-empty value. If your code relies on the presence of a UUID in responses, ensure it is defined for each user, and prefer endpoints that provide more details.
	>
	> Regardless of individual user status, make sure to check for existence before attempting to use the value of the `uuid` field.

[bc-terra]

@bc-Vince how's this for a revision?

[bc-Vince]

@bc-terra This looks great to me!