##### SUMMARY

When I run `ansible-galaxy [type] init`, I would like to be able to use my own configured 'skeleton' to init that content.

For Ansible roles, when running `ansible-galaxy role init myrole`, I can configure a [`GALAXY_ROLE_SKELETON`](https://docs.ansible.com/ansible/latest/reference_appendices/config.html#galaxy-role-skeleton) in my `ansible.cfg`, and the init command will use that skeleton as the source for the new role.

For Ansible collections, currently there's a bug (https://github.com/ansible/ansible/issues/66255) that causes collections to use that skeleton if its set (which can lead to some confusion)—but once that bug's fixed, there's no way to specify a skeleton for a collection.

So this feature request is to add a new configuration option `GALAXY_COLLECTION_SKELETON` (environment variable `ANSIBLE_GALAXY_COLLECTION_SKELETON`) which allows a collection skeleton to be specified.

Note: the docs for `GALAXY_ROLE_SKELETON` currently state:

> Role or collection skeleton directory to use as a template for the `init` action in `ansible-galaxy`, same as `--role-skeleton`.

Therefore that would need adjusting too, if the previously mentioned bug doesn't fix that.

##### ISSUE TYPE
- Feature Idea

##### COMPONENT NAME

ansible-galaxy init

##### ADDITIONAL INFORMATION

N/A
"""
        Install one or more roles(``ansible-galaxy role install``), or one or more collections(``ansible-galaxy collection install``).
        You can pass in a list (roles or collections) or use the file
        option listed below (these are mutually exclusive). If you pass in a list, it
        can be a name (which will be downloaded via the galaxy API and github), or it can be a local tar archive file.
        :param artifacts_manager: Artifacts manager.
        """
        install_items = context.CLIARGS['args']
        requirements_file = context.CLIARGS['requirements']
        collection_path = None
        if requirements_file: