Enable Visual Debugging for ClientLibs Load Failures in Author Environment

[#1]

Request for Feature Enhancement (RFE) Summary:	Introduce a built-in visual debugging tool in AEM Author to detect and highlight failed ClientLibs loading (eg. 404s, category mismatches).
Use-case:	AEM pages often break in layout or functionality due to missing or incorrectly loaded ClientLibs, especially during template development or after dispatcher/CDN deployments. Authors and content editors face difficulties identifying these issues quickly without browser dev tools expertise.
Current/Experienced Behavior:	Missing ClientLibs result in broken layouts, JS errors, or missing styles/scripts - but no warnings are visible to non-technical users on the page itself. Only browser dev tools or logs reveal these issues, making root cause analysis slow.
Improved/Expected Behavior:	AEM should highlight missing ClientLibs visually on the page, or provide a debugging overlay or console warning for authors. This should include category mismatch detection, permission issues, and HTTP error codes for assets.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEM as a Cloud Service; observed in multiple environments with Dispatcher/CDN caching layers.
Customer-name/Organization name:
Screenshot (if applicable):
Code package (if applicable):