[Draft] [MWPW-179252] Add pageConfig call for optimal endpoint

[vipu0303]

https://jira.corp.adobe.com/browse/MWPW-179252

• Added changes to make pageConfig call and update the endpoint
• Making all calls (including analytics) to the updated end point further
• Made the method generic so that it can be called across different workflows
• sending updated endpoint to slytherin for sending analytics to updated endpoint
• send pageConfig analytics (both success and failure, changes done in slytherin code for this)
• [ToDo] UTs are yet to be added

Corresponding Slytherin PR:
adobecom/dc#1295

Resolves: MWPW-179252

Test URLs:

• Before: https://stage--dc--adobecom.aem.page/acrobat/online/pdf-to-png
• After: https://stage--dc--adobecom.aem.page/acrobat/online/pdf-to-png?unitylibs=pageConfig

[aem-code-sync]

Hello, I'm the AEM Code Sync Bot and I will run some actions to deploy your branch and validate page speed.
In case there are problems, just click a checkbox below to rerun the respective action.

• Re-run PSI checks
• Re-sync branch

Commits

• e1e7082 ✅ (latest)
• 397fce2 ✅
• 90aac4c ✅
• 0066bc6 ✅
• 20b2848 ✅
• a83defa ✅
• 2b8696c ✅
• dc8853c ✅
• 5c4620b ✅
• d06c44d ✅
• eda0c0f ✅
• e207af4 ✅

[vipu0303]

slytherin (dc) side changes corresponding to this are in PR:
adobecom/dc#1295

[arugupta1992]

check if the dashboard query needs modification to start recording this. Actual modification to be done after the PR merge

[vipu0303]

yes, it may need dashboard modifications.

[arugupta1992]

Suggested change

	async checkandUpdatePageConfigEndpoint(updateConfigCallback, onFailure) {
	async updateUnityEndpoint(updateConfigCallback, onFailure) {

[vipu0303]

updated the name to fetchPageConfig.
The method now accepts unityEndpointSuccessCb and unityEndpointfailureCb and also returns the response body which make it future proof in case more info is being fetched from service in response.