This might help you https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-forms/publishing-error-failed-to-retrieve-references-for-selected/td-p/213854

The last installed one irrespective of version number

I believe you can implement lazy loading for images but not for js and css.

I believe latest install package/bundle always take precedence over the last install package/bundle with same name 

I believe to call a component or service based on selector the selector should be part of request url and not with htl. If your component has selector.htl it will automatically get called but in this case you need to call the component selector via page jcr:content component path

It should provide you the node path and not the page. Can you  check with random node present on the result if that’s value is present there or not. My be you need to look for other text in full text that describes or limits your search to the expected result 

path=/content/xxx fulltext=aem orderby=path p.limit=-1   above query works for me

Full text query is working for me in my local. The result is giving the authored node path.   are you referring to have the authored value as well in query results?

The initial screenshot is not so clear to me. Can you share the good quality screenshots of your content node highlighting the value that you wants to search   

Hi this query works on my side   path=/content/xxxtype=cq:pageproperty=sling:resourceType property.value=your authored component pathorderby=pathp.limit=-1  other one is path=/content/xxxtype=cq:pageproperty=jcr:content/redirectTargetproperty.operation=exists orderby=path p.limit=-1