Which default create drop-down menu are you referring to? Can you be more specific 

instead of custom metadata field for this on you should be using the create review task workflow to have this on your assets and you can control who can approve or reject will be controlled by group that has the permission of doing the review.

Are you using Java 11 or java 8? It seems the maven-scr-plugin that you are using is not being supported by Java that you are using. Latest version of maven-scr-plugin supports java11 and if you are using java 11 try moving to latest version of maven-scr-plugin which is 1.26.4

Why don’t you try this one for sass compiler support on aem https://github.com/mickleroy/aem-sass-compiler

Why don’t you create a maven archetype project on your local using the project archetype instead of downloading the project archetype from any other git repo

You can only control the rootpath to allow selection inside certain paths using rootpath property using docs https://developer.adobe.com/experience-manager/reference-materials/6-5/granite-ui/api/jcr_root/libs/granite/ui/components/coral/foundation/picker/index.htmland if your use case is to only all...

It seems with publishing the node from author to publisher it’s calling the auto invalidate feature of your aem dispatcher which also depends on the statfilelevel . please check this document to understand the statfilelevel and invalidate section https://experienceleague.adobe.com/docs/experience-ma...

Actually when you create a custom metadata fir assets in aem it saved at conf/global/settings/dam/adminui-extension. Since your log suggest that it doesn’t have the jcr:content Child resource, I suspect that on prod you don’t have custom metadata created. Can you please check if custom metadata node...

Do you see more than one bundle of your project as well installed on your aem instance?

Classic component won’t work in touch ui editor as node definition is different there and since adobe has officially depreciated the support of classic ui so you left of no other option to convert the component to touch ui