Custom devcontainer folder name when developing features locally

I am exploring the idea of using a `devcontainer` as a portable toolbox. The main idea is to have a repo that just constitutes what would be the usual `.devcontainer` folder. The problem is that I do not want to use that name, to not clash with that name if the project I use it within is already using devcontainers.

The idea is that through locally developed features, I could create a number of scripts (e.g., local `uv` tools) that I can just use within any project (and benefit of the ease of mounting of devcontainers).

All works really well, and I am happy where this is going, but the main problem is that to reference a feature that lives locally, I must have a `.devcontainer` folder. For the rest, I can call the folder whatever I want and just pass a `--config` flag.

Is there any chance where that constraint is removed and locally referenced features work in any arbitrary folder? Maybe the parent folder of where `--config` is pointing to?

Start by tracing the CLI's --config handling and the code that resolves locally referenced features. Check how the current .devcontainer requirement is enforced and whether related tests cover arbitrary config locations. Done means a locally referenced feature works from an arbitrary folder without requiring the .devcontainer name.

Written by the indexing model from the issue text.