### 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
'Collection',
                        'Version',
                        fqcn_width,
                        version_width
                    )
                    seen.add(collection_path)
                _display_collection(collection, fqcn_width, version_width)
        path_found = False
        for path in collections_search_paths:
            if not os.path.exists(path):
                if path in default_collections_path:
                    
                    continue
                warnings.append("- the configured path {0} does not exist.".format(path))
            elif os.path.exists(path) and not os.path.isdir(path):
                warnings.append("- the configured path {0}, exists, but it is not a directory.".format(path))
            else:
                path_found = True
        
        if collection_found and collection_name:
            warnings = []
        for w in warnings:
            display.warning(w)
        if not collections and not path_found:
            raise AnsibleOptionsError(
                "- None of the provided paths were usable. Please specify a valid path with --{0}s-path".format(context.CLIARGS['type'])
            )
        if output_format == 'json':
            display.display(json.dumps(collections_in_paths))
        elif output_format == 'yaml':