Check this package on your depfinder - i am seeing it fine: http://localhost:4502/system/console/depfinder

Can you please show a screen shot of the component and its nodes you are using. There may be another way to do what you are trying to accomplish.In case you missed something - here is the technical docs - aem-core-wcm-components/content/src/content/jcr_root/apps/core/wcm/components/form/options/v2/o...

I have never read anywhere in AEM documentation that dispatcher supports this functionality. Lets see what other community members have to say on this use case. 

You stated -- "I still haven't been able to get the dropdown list to populate in a published environment."Are you trying to set a component dialog on PUBLISH?

Are you seeing any log messages. Also - when you fix the issue via:editing any component's cq:editConfig/@cq:actions property through the CRXDE and saving.Are you seeing the issue occur on the same dialog?

From 6.3 on - Adobe recommends that you use editable templates. You should use editable templates, set policies (that control which components are authorable (in the page) in the layout container) and then set fixed components (like footers and headers) in the editable template.For more information ...

As Sumeet correctly answered - you can use the CRX2OAK migration tool.

The issue you have is there is not a lot of docs on how to modify the asset metadata editor.There is this - Extending Asset EditorI checked with the Eng team too - they recommend that you look here: Adobe Experience Manager Help | Cascading Metadata

I would log a bug against this part of AEM and in mean time - you can use the workaround you found.

What AEM version are you using. Also what multifield granite type are you using.