##### SUMMARY

Ansible galaxy collection installation in command line fails when parameter is an URL.

```Shell
ansible-galaxy collection install http://repo.company.com/ansible-collection/my_namespace-my_collection-0.1.tar.gz
Process install dependency map
ERROR! Invalid collection name 'http', name must be in the format <namespace>.<collection>.
```

##### ISSUE TYPE
- Bug Report

##### COMPONENT NAME

**ansible-galaxy**

*collection_name* as url parameter should be supported according the documentation:

```Shell
ansible-galaxy collection install -h

positional arguments:
  collection_name       The collection(s) name or path/url to a tar.gz
                        collection artifact. This is mutually exclusive with
                        --requirements-file.
```

##### ANSIBLE VERSION

```
ansible 2.9.1
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/home/ubuntu/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /tmp/venv-project/local/lib/python2.7/site-packages/ansible
  executable location = /tmp/venv-project/bin/ansible
  python version = 2.7.15+ (default, Oct  7 2019, 17:39:04) [GCC 7.4.0]
```

##### CONFIGURATION

```
DEFAULT_VAULT_PASSWORD_FILE(env: ANSIBLE_VAULT_PASSWORD_FILE) = /home/ubuntu/.ansible/.vault-dev.txt
HOST_KEY_CHECKING(/etc/ansible/ansible.cfg) = False
```

##### OS / ENVIRONMENT

OS : Ubuntu. Ansible usage via native *apt* package or *pip*.

##### STEPS TO REPRODUCE

Create some ansible collection and publish/upload it on some http endpoint: `http://repo.company.com/ansible-collection/my_namespace-my_collection-0.1.tar.gz`

Installation via local file is working fine (=> collection package is correct):
```Shell
rm -rf ~/.ansible/collections/
wget http://repo.company.com/ansible-collection/my_namespace-my_collection-0.1.tar.gz
ansible-galaxy collection install my_namespace-my_collection-0.1.tar.gz

Process install dependency map
Starting collection install process
Installing 'my_namespace-my_collection:0.1-SNAPSHOT' to '/home/ubuntu/.ansible/collections/ansible_collections/my_namespace/my_collection'
```

Installation via [requirement file](https://docs.ansible.com/ansible/latest/galaxy/user_guide.html#install-multiple-collections-with-a-requirements-file) (like #61680) is working fine too:

With `requirements.yml`:

```YAML
---
collections:
- name: http://repo.company.com/ansible-collection/my_namespace-my_collection-0.1.tar.gz
```

```Shell
rm -rf ~/.ansible/collections/
ansible-galaxy collection install -r requirements.yml

Process install dependency map
Starting collection install process
Installing 'my_namespace-my_collection:0.1-SNAPSHOT' to '/home/ubuntu/.ansible/collections/ansible_collections/my_namespace/my_collection'
```

But using command line installation fails:

```Shell
rm -rf ~/.ansible/collections/
ansible-galaxy collection install http://repo.company.com/ansible-collection/my_namespace-my_collection-0.1.tar.gz
Process install dependency map
ERROR! Invalid collection name 'http', name must be in the format <namespace>.<collection>.
```

##### EXPECTED RESULTS

```Shell
Installing 'my_namespace-my_collection:0.1-SNAPSHOT' to '/home/ubuntu/.ansible/collections/ansible_collections/my_namespace/my_collection'
```

##### ACTUAL RESULTS

```Shell
ERROR! Invalid collection name 'http', name must be in the format <namespace>.<collection>.
```

---
            roles:
            # Same as v1 format just under the roles key
            collections:
            - namespace.collection
            - name: namespace.collection
              version: version identifier, multiple identifiers are separated by ','
              source: the URL or a predefined source name that relates to C.GALAXY_SERVER_LIST
        :param requirements_file: The path to the requirements file.
        :param allow_old_format: Will fail if a v1 requirements file is found and this is set to False.
        :return: a dict containing roles and collections to found in the requirements file.
        """
        requirements = {
            'roles': [],
            'collections': [],
        }
        b_requirements_file = to_bytes(requirements_file, errors='surrogate_or_strict')
        if not os.path.exists(b_requirements_file):
            raise AnsibleError("The requirements file '%s' does not exist." % to_native(requirements_file))
        display.vvv("Reading requirement file at '%s'" % requirements_file)
        with open(b_requirements_file, 'rb') as req_obj:
            try:
                file_requirements = yaml.safe_load(req_obj)
            except YAMLError as err:
                raise AnsibleError(
                    "Failed to parse the requirements yml at '%s' with the following error:\n%s"
                    % (to_native(requirements_file), to_native(err)))
        if requirements_file is None:
            raise AnsibleError("No requirements found in file '%s'" % to_native(requirements_file))
        def parse_role_req(requirement):