feat: ability to set and modify the default project

[CaptainStandby]

Adds the new command use project to the cli that can be used to manipulate the selected project.

Examples

1. Calling use without id will echo the currently selected project id

$ ory use project
ID      121035f0-5d74-472b-8cc3-39fd727fdfd2

2. Calling use with id will set the currently selected project

$ ory use project c2e150b3-63cf-4aeb-998e-8250a748c108
ID      c2e150b3-63cf-4aeb-998e-8250a748c108

3. Calling a command that previously required a project id will now use the selected project when no id is provided

$ ory get project
ID      121035f0-5d74-472b-8cc3-39fd727fdfd2
SLUG    zen-napier-otwc45scr7
STATE   running
NAME    MyProject

4. When creating a new project the newly created project was previously set as the selected project. This has been changed to only set the selected project when --use-project is provided or the currently selected project is invalid.

$ ory create project --name doIt --use-project
Project created successfully!
ID      c0b9df27-4650-4c7b-9c29-37f499503d6a
SLUG    nervous-allen-47ubo7x9ew
STATE   running
NAME    doIt

$ ory use project
ID      c0b9df27-4650-4c7b-9c29-37f499503d6a

$ ory create project --name no-use              
Project created successfully!
ID      81f9df40-8a45-45e0-9d35-15a67f9840c5
SLUG    lucid-ride-guygrtm16y
STATE   running
NAME    no-use

$ ory use project
ID      c0b9df27-4650-4c7b-9c29-37f499503d6a

Related Issue or Design Document

closes #154

Checklist

• I have read the contributing guidelines
  and signed the CLA.
• I have referenced an issue containing the design document if my change
  introduces a new feature.
• I have read the security policy.
• I confirm that this pull request does not address a security
  vulnerability. If this pull request addresses a security vulnerability, I
  confirm that I got approval (please contact
  security@ory.sh) from the maintainers to push
  the changes.
• I have added tests that prove my fix is effective or that my feature
  works.
• I have added the necessary documentation within the code base (if
  appropriate).

Further comments

[aeneasr]

I have not done a full code review yet, but from a high level this looks very good :) Nice job! I will try to do a detailed code review in the next days

[aeneasr]

When creating a new project the newly created project was previously set as the selected project. This has been changed to only set the selected project when --use-project is provided or the currently selected project is invalid.

In the documentation, we will probably need to use this flag everywhere, because we often would do:

ory create project --use-project --name ...
ory ...

In my mind, when I create a project, I usually want to continue modifying it. My proposal would be to reverse this logic:

ory create project --dont-use

WDYT?

[CaptainStandby]

When creating a new project the newly created project was previously set as the selected project. This has been changed to only set the selected project when --use-project is provided or the currently selected project is invalid.

In the documentation, we will probably need to use this flag everywhere, because we often would do:

ory create project --use-project --name ...
ory ...

In my mind, when I create a project, I usually want to continue modifying it. My proposal would be to reverse this logic:

ory create project --dont-use

WDYT?

I'm not a big fan of implicit side effects as in my experience they often tend to cause confusion and unexpected behaviour. For the documentation I would probably recommend not to rely on the "current project" logic at all and always be specific for this exact reason.

For the special case when a project is created and no default was set, the default is implicitly set to the newly created project, which is fine in this context.

[aeneasr]

Point made, point taken :)

[aeneasr]

@hperl could you maybe help out with a review here? :)

[hperl]

This looks really good already 🎉. I especially like the thorough testing 🤩. I added some remarks below.

[aeneasr]

Great :) Thank you for paying extra attention in the tests! Generally speaking, this looks quite good to me. There are two comments related to Go standards. Similar to Henning, I suggest to reduce the duplication in the tests. Especially for larger tests (such as patch) it's adding way too much bloat.

I left a comment which could help you implement the tests without duplication. We use this pattern already quite extensively in Ory Kratos

[hperl]

Very nice, LGTM 🎉

[aeneasr]

Great job!