Set environment context

In cases of fast iteration while refactoring to remove vulnerabilities, the information is noisy, or trashy information that I wouldn’t like to have related to the organization, so I don't want to push these images into the Docker Scout platform. But, it is useful information and so it would useful to use local/image to identify those changes that are not ready yet.

It would be great if Docker Scout had the context of the org I'm in, and the environment/stage I am in. Analogous to git having folder and branch context. So for example, I could be warned if I try to register an image that's still in flux. Eg “You’re logged into [org name] and trying to register a local image”. This would help avoid clutter, consuming plan resources, hitting limits, etc within the Docker Scout platform.

Start by tracing the CLI flow for registering a local image and how Docker Scout organization context is currently obtained. Clarify how organization and environment or stage should be represented, and define the warning and registration behavior for images still in flux. Done means the intended context model and user-facing behavior are agreed and covered by tests.