##### SUMMARY
2.9/devel currently supports relative Python imports inside a collection for all but modules/module_utils. Extend the AnsiballZ analysis/bundling to support relative imports for those as well.

##### ISSUE TYPE
- Feature Idea

##### COMPONENT NAME
module_common.py

##### ADDITIONAL INFORMATION
This is needed to minimize the number of places a collection must refer to itself by name. Also a convenience for shorter intra-collection Python imports (eg `from ..module_utils.blah import AThing` vs. `from ansible_collections.myns.mycoll.plugins.module_utils.blah import AThing`)
"""
    PluginLoader optimized for Jinja2 plugins
    The filter and test plugins are Jinja2 plugins encapsulated inside of our plugin format.
    The way the calling code is setup, we need to do a few things differently in the all() method
    """
    def find_plugin(self, name, collection_list=None):
        
        
        if '.' in name:
            return super(Jinja2Loader, self).find_plugin(name, collection_list=collection_list)
        raise AnsibleError('No code should call find_plugin for Jinja2Loaders (Not implemented)')
    def get(self, name, *args, **kwargs):