Both config and manifest files in subdirectory, but refer to repo root for package?

Hey there,

**What I'm trying to do**

I'm trying to store my various CI tool configs files in a single `.ci` subdirectory at the repo root. This way, I can avoid having various dotfiles alongside the user's code.

I'm instantiating the RP action as follows:

```
- uses: googleapis/release-please-action@v4
with:
token: ${{ secrets.GITHUB_TOKEN }}
config-file: .ci/release-please-config.json
manifest-file: .ci/release-please-manifest.json
```

And the contents of each of these files:

**config**
```
{
"release-type": "python"
}
```

**manifest**
```
{
".": "1.0.1"
}
```

**The error I'm seeing**

Not so much an error as more of a notification, that no releases have been found with a "null" component.. and this is not configured in the manifest. I've tried various approaches (`include-component-in-tag` true/false, change the `path` to be `../`, etc - but I read that this is no supported for security reasons) - all yield the same output below:

```
❯ Fetching .ci/release-please-config.json from branch main
❯ Fetching .ci/release-please-manifest.json from branch main
✔ Building releases
✔ Building strategies by path
❯ Fetching .ci/release-please-config.json from branch main
❯ Fetching .ci/release-please-manifest.json from branch main
✔ Building pull requests
✔ Building strategies by path
✔ Collecting release commit SHAs
❯ release search depth: 400
❯ Fetching releases with cursor undefined
⚠ Found release tag with component '', but not configured in manifest
⚠ Found release tag with component '', but not configured in manifest
✔ Collecting commits since all latest releases
⚠ Found release tag with component '', but not configured in manifest
⚠ Found release tag with component '', but not configured in manifest
❯ commit search depth: 500
❯ Set(0) {}
```

The tags in my repo:

```
v0.1.0
v0.2.0
v1.0.0
v1.0.1
```

**The question**

Is it possible to store both the config and the manifest in a subdirectory (for tidiness) and still have RP refer to the root of the repo for the package (as per the special-handling `.` path?

Thanks!