Enhancing SPA Deployment Flexibility in AEM with Adapter Layer and Multi-field Mapping

[#1]

Request for Feature Enhancement (RFE) Summary:	Having an editorial feature to configure mapping of JSON fields
Use-case:	To decouple SPA deployments from Adobe Experience Manager (AEM), Having an adapter layer that facilitates dynamic mapping of JSON fields between AEM components and frontend SPA components. This approach ensures that changes in frontend development require minimal configuration in AEM, promoting a more agile and independent deployment process.
Current/Experienced Behavior:	SPA deployment has to align with AEM deployments whilst mock data mapping in place.
Improved/Expected Behavior:	Realtime testing in pre-prod environments before hand. Also, helps in productivity by reducing dependencies in wider teams(Infra Dev and QA)
Environment Details (AEM version/service pack, any other specifics if applicable):	AEMaaCS
Customer-name/Organization name:	PremierLeague
Screenshot (if applicable):
Code package (if applicable):