Fix the AEM authoring interface when the debugClientLibs query param is set

[#1]

Request for Feature Enhancement (RFE) Summary:	The AEM Authoring interface doesn't work with the debugClientLibs query param so debugging client libraries is not possible anymore.
Use-case:	There is a documented parameter debugClientLibs that produces client libraries output in the debug mode, without combining and minifying the JS and CSS files. It was very useful in the early versions of AEM but stopped working some time ago, either due to new out-of-the-box client libraries or because of those libraries' modifications, or because of the evolution of modern web browsers. It would be good to have it back.
Current/Experienced Behavior:	The authoring interface doesn't work correctly when there is documented debugClientLibs=true parameter present in the query.
Improved/Expected Behavior:	The authoring interface should work when the debugClientLibs=true parameter is set in the query
Environment Details (AEM version/service pack, any other specifics if applicable):	Stopped working since AEM 6.3 (roughly). Tested on Chrome only.
Customer-name/Organization name:	Media.Monks
Screenshot (if applicable):
Code package (if applicable):

[#2]

@yuriy_shestakov 

Thanks for proposing this idea

This has been reported to the engineering under the internal reference SITES-14947. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.

[#3]

@yuriy_shestakov Comment from PM team: To debug the page, developers can still use this debugClientLibs parameter by loading the page outside of the editor. This issue addresses only a very limited audience: developers debugging their implementation, and it does have a workaround. Also, the whole focus and priorities are on the Universal Editor, therefore, this is declined. 

Should you have more comments on this, please feel free to share them here.