##### 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
min_ansible_version=ansible_version[:3],  
                dependencies=[],
            ))
            obj_path = os.path.join(init_path, obj_name)
        elif galaxy_type == 'collection':
            namespace, collection_name = obj_name.split('.', 1)
            inject_data.update(dict(
                namespace=namespace,
                collection_name=collection_name,
                version='1.0.0',
                readme='README.md',
                authors=['your name <example@domain.com>'],
                license=['GPL-2.0-or-later'],
                repository='http://example.com/repository',
                documentation='http://docs.example.com',
                homepage='http://example.com',
                issues='http://example.com/issue/tracker',
                build_ignore=[],
            ))
            obj_path = os.path.join(init_path, namespace, collection_name)
        b_obj_path = to_bytes(obj_path, errors='surrogate_or_strict')
        if os.path.exists(b_obj_path):
            if os.path.isfile(obj_path):
                raise AnsibleError("- the path %s already exists, but is a file - aborting" % to_native(obj_path))
            elif not force:
                raise AnsibleError("- the directory %s already exists. "
                                   "You can use --force to re-initialize this directory,\n"
                                   "however it will reset any main.yml files that may have\n"
                                   "been modified there already." % to_native(obj_path))
        if obj_skeleton is not None: