### Summary

When I install a collection that depends on another collection that I already have installed, installation fails with `--offline`, while it shouldn't need to.

### Issue Type

Bug Report

### Component Name

galaxy

### Ansible Version

```console
$ ansible --version
ansible [core 2.14.1]
  config file = None
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.11/site-packages/ansible
  ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
  executable location = /usr/local/bin/ansible
  python version = 3.11.1 (main, Dec 21 2022, 18:32:57) [GCC 10.2.1 20210110] (/usr/local/bin/python)
  jinja version = 3.1.2
  libyaml = True
```


### Configuration

```console
# if using a version older than ansible-core 2.12 you should omit the '-t all'
$ ansible-config dump --only-changed -t all
CONFIG_FILE() = None
```


### OS / Environment

Debian 11

### Steps to Reproduce

```sh
➤ podman container run --rm -it python:3.11 bash -c 'pip install -q ansible==7.1.0 && wget -q https://galaxy.ansible.com/download/geerlingguy-mac-2.1.1.tar.gz && ansible-galaxy collection list community.general && ansible-galaxy -vvvv collection install --offline ./geerlingguy-mac-2.1.1.tar.gz'
```

### Expected Results

Collection `geerlingguy.mac` installed.

### Actual Results

```console
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

# /usr/local/lib/python3.11/site-packages/ansible_collections
Collection        Version
----------------- -------
community.general 6.1.0  
Starting galaxy collection install process
Process install dependency map
ERROR! Failed to resolve the requested dependencies map. Could not satisfy the following requirements:
* community.general:>=3.0.0 (dependency of geerlingguy.mac:2.1.1)
```


### Code of Conduct

- [X] I agree to follow the Ansible Code of Conduct
galaxy_type = 'collection' if parser.metavar == 'COLLECTION_ACTION' else 'role'
        init_parser = parser.add_parser('init', parents=parents,
                                        help='Initialize new {0} with the base structure of a '
                                             '{0}.'.format(galaxy_type))
        init_parser.set_defaults(func=self.execute_init)
        init_parser.add_argument('--init-path', dest='init_path', default='./',
                                 help='The path in which the skeleton {0} will be created. The default is the '
                                      'current working directory.'.format(galaxy_type))
        init_parser.add_argument('--{0}-skeleton'.format(galaxy_type), dest='{0}_skeleton'.format(galaxy_type),
                                 default=C.GALAXY_COLLECTION_SKELETON if galaxy_type == 'collection' else C.GALAXY_ROLE_SKELETON,
                                 help='The path to a {0} skeleton that the new {0} should be based '
                                      'upon.'.format(galaxy_type))
        obj_name_kwargs = {}
        if galaxy_type == 'collection':
            obj_name_kwargs['type'] = validate_collection_name
        init_parser.add_argument('{0}_name'.format(galaxy_type), help='{0} name'.format(galaxy_type.capitalize()),
                                 **obj_name_kwargs)
        if galaxy_type == 'role':
            init_parser.add_argument('--type', dest='role_type', action='store', default='default',
                                     help="Initialize using an alternate role type. Valid types include: 'container', "
                                          "'apb' and 'network'.")
    def add_remove_options(self, parser, parents=None):