### 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
req_fd.write(yaml_bytes)
def publish_collection(collection_path, api, wait, timeout):
    """Publish an Ansible collection tarball into an Ansible Galaxy server.
    :param collection_path: The path to the collection tarball to publish.
    :param api: A GalaxyAPI to publish the collection to.
    :param wait: Whether to wait until the import process is complete.
    :param timeout: The time in seconds to wait for the import process to finish, 0 is indefinite.
    """
    import_uri = api.publish_collection(collection_path)
    if wait:
        
        
        
        
        task_id = None
        for path_segment in reversed(import_uri.split('/')):
            if path_segment:
                task_id = path_segment
                break
        if not task_id:
            raise AnsibleError("Publishing the collection did not return valid task info. Cannot wait for task status. Returned task info: '%s'" % import_uri)
        with _display_progress(
                "Collection has been published to the Galaxy server "
                "{api.name!s} {api.api_server!s}".format(api=api),
        ):
            api.wait_import_task(task_id, timeout)
        display.display("Collection has been successfully published and imported to the Galaxy server %s %s"
                        % (api.name, api.api_server))
    else:
        display.display("Collection has been pushed to the Galaxy server %s %s, not waiting until import has "