#11795 preserve order of bean-defined basenames
Rebasing https://github.com/apache/grails-core/issues/11795 onto 7.0.x
@robertoschwald I see you submitted this PR sometime ago and it was never merged. From what I can tell, it's still an issue. I don't see any tests in the original PR, are you willing to add tests for this? If so, I'm happy to merge this into 7.0.0.
The problem with bundle ordering materalized here when adding a PluginAwareResourceBundleMessageSource messageSource definition and sets own basenames to be able to overwrite other bundles keys in a centralized bundle file. Then the plugin basenames were first in the list, not last.
See #14755
I would expect to see a failing test in ResourceBundleMessageSourceSpec after resetting the changes to PluginAwareResourceBundleMessageSource.