### 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
display.display(yaml_dump(collections_in_paths))
        return 0
    def execute_publish(self):
        """
        Publish a collection into Ansible Galaxy. Requires the path to the collection tarball to publish.
        """
        collection_path = GalaxyCLI._resolve_path(context.CLIARGS['args'])
        wait = context.CLIARGS['wait']
        timeout = context.CLIARGS['import_timeout']
        publish_collection(collection_path, self.api, wait, timeout)
    def execute_search(self):
        ''' searches for roles on the Ansible Galaxy server'''
        page_size = 1000
        search = None
        if context.CLIARGS['args']:
            search = '+'.join(context.CLIARGS['args'])
        if not search and not context.CLIARGS['platforms'] and not context.CLIARGS['galaxy_tags'] and not context.CLIARGS['author']:
            raise AnsibleError("Invalid query. At least one search term, platform, galaxy tag or author must be provided.")
        response = self.api.search_roles(search, platforms=context.CLIARGS['platforms'],
                                         tags=context.CLIARGS['galaxy_tags'], author=context.CLIARGS['author'], page_size=page_size)
        if response['count'] == 0:
            display.display("No roles match your search.", color=C.COLOR_ERROR)
            return True
        data = [u'']
        if response['count'] > page_size:
            data.append(u"Found %d roles matching your search. Showing first %s." % (response['count'], page_size))
        else:
            data.append(u"Found %d roles matching your search:" % response['count'])
        max_len = []
        for role in response['results']: