### Summary

```(venv) ➜  ansible-navigator git:(main) ansible-galaxy collection install cisco.ios -p ./collections
Starting galaxy collection install process
[WARNING]: The specified collections path '/Users/bthornto/github/ansible-navigator/collections' is not part of the configured Ansible collections paths '/Users/bthornto/.ansible/collections:/usr/share/ansible/collections'. The installed collection won't be
picked up in an Ansible run.
```
It will be picked up in an Ansible run, in fact playbook adjacent collections are fully Supported.

Can `, unless within a playbook adjacent collections directory` be added to the message?

### Issue Type

Bug Report

### Component Name

ansible-galaxy

### Ansible Version

```console
$ ansible --version

ansible [core 2.11.0]
  config file = None
  configured module search path = ['/Users/bthornto/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /Users/bthornto/github/ansible-navigator/venv/lib/python3.8/site-packages/ansible
  ansible collection location = /Users/bthornto/.ansible/collections:/usr/share/ansible/collections
  executable location = /Users/bthornto/github/ansible-navigator/venv/bin/ansible
  python version = 3.8.2 (default, Dec 21 2020, 15:06:04) [Clang 12.0.0 (clang-1200.0.32.29)]
  jinja version = 3.0.0
  libyaml = True
```


### Configuration

```console
$ ansible-config dump --only-changed
```


### OS / Environment

all

### Steps to Reproduce

<!--- Paste example playbooks or commands between quotes below -->
```shell
(venv) ➜  ansible-navigator git:(main) ansible-galaxy collection install cisco.ios -p ./collections
Starting galaxy collection install process
[WARNING]: The specified collections path '/Users/bthornto/github/ansible-navigator/collections' is not part of the configured Ansible collections paths '/Users/bthornto/.ansible/collections:/usr/share/ansible/collections'. The installed collection won't be
picked up in an Ansible run.
```


### Expected Results

warning messages indicates that if the installation directory is playbook adjacent and called collections it will be picked up by ansible while running the playbook

### Actual Results

```console
received somewhat invalid warning message
```


### Code of Conduct

- [X] I agree to follow the Ansible Code of Conduct
return os.path.abspath(os.path.expanduser(os.path.expandvars(path)))
    @staticmethod
    def _get_skeleton_galaxy_yml(template_path, inject_data):
        with open(to_bytes(template_path, errors='surrogate_or_strict'), 'rb') as template_obj:
            meta_template = to_text(template_obj.read(), errors='surrogate_or_strict')
        galaxy_meta = get_collections_galaxy_meta_info()
        required_config = []
        optional_config = []
        for meta_entry in galaxy_meta:
            config_list = required_config if meta_entry.get('required', False) else optional_config
            value = inject_data.get(meta_entry['key'], None)
            if not value:
                meta_type = meta_entry.get('type', 'str')
                if meta_type == 'str':
                    value = ''
                elif meta_type == 'list':
                    value = []
                elif meta_type == 'dict':
                    value = {}
            meta_entry['value'] = value
            config_list.append(meta_entry)
        link_pattern = re.compile(r"L\(([^)]+),\s+([^)]+)\)")
        const_pattern = re.compile(r"C\(([^)]+)\)")
        def comment_ify(v):