Edit EMA: Provide Better APIs in dotCMS JavaScript SDK

[fmontes]

Parent

#26644

User Story

As a developer, I want to have access to additional fetch options when initializing the dotCMS client library so that I can have more control over the API calls made by the SDK.

Additionally, I would like to have a more intuitive API structure, where instead of using client.getPage and client.getNav, I can use client.page.get and client.nav.get.

Acceptance Criteria

Preview Give feedback

1. Users should be able to add fetch options when initializing the dotCMS client library.
2. client.getNav should be now client.nav.get
3. client.getPage should be now client.page.get

Proposed Objective

Core Features

Proposed Priority

Priority 3 - Average

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

1. For the client fetch option, use the native types, but we should omit method and body and maybe something else, we need to do some research here.
2. When changing the API consider that it could grow, for example: client.page.save or client.workflow.trigger.

Assumptions & Initiation Needs

• The existing dotCMS JavaScript SDK codebase will need to be modified to accommodate the new features.
• The dotCMS API should be able to handle the additional fetch options provided by the SDK.

Quality Assurance Notes & Workarounds

• Test the new fetch options when initializing the dotCMS client library to ensure they