Option A
I see that the file /libs/.../infopanel.jsp is loading the following client library:
<ui:includeClientLib categories="cq.gui.coral.common.admin.toolbar.infopanel"/>You should be able to create your own custom client library and assign it the category name "cq.gui.coral.common.admin.toolbar.infopanel." This will allow it to load alongside the existing AEM code. If this approach doesn't work, consider overriding the infopanel.jsp file, as described in Option B below.
Option B
Directly overriding a .jsp file in AEM as a Cloud Service is possible using the Sling Resource Merger framework. The key is to recreate the exact path of the target file under your /apps folder.
You'll need to set up the following folder structure within the ui.apps module of your AEM Maven project. Now, create the infopanel.jsp file at the specified path (/apps/dam/.../infopanel.jsp). This file will override the default one and also include your new client library.
< code of infopanel.jsp as taken from AEM >
<%-- Here you can load your custom clientlib --%>
<ui:includeClientLib categories="your.custom.category.toolbar.infopanel"/>Now you can create a new folder for your client library. A good practice is to place it under a project-specific path.
/apps
└── /your-project-name
└── /clientlibs
└── /clientlib-search-override
More info on how to create and using a clientlib
here and
here.