feat: resolve project-id and org-id using instance-id

[LucDeCaf]

Replaces #37 using a cleaner and (hopefully) simpler approach.

---

Using a newly introduced path in @powersync/management-client, automatically fetch the project_id and org_id flags when given the instance_id for a number of commands (where it makes sense to do so).

Example

Before:

powersync pull instance --project-id='project-123-456-789' --instance-id='instance-123-456-789'

After:

# Project ID is fetched from the management service if required
powersync pull instance --instance-id='instance-123-456-789'

AI Usage

Claude Code was used to update documentation and examples to reflect the new paths. It was also used for simple edits/refactors (e.g. moving a constant to be exported from a shared file).

[stevensJourney]

This looks like it's going in a good direction. I'm happy with the implementation so far.

I left a few minor comments on some lines which stood out.

I think the main outstanding item currently is that of docs: both externally in our powersync-docs site (and agent skills) and here in the various README and docs files. We should update all references to commands which no longer need to supply the org/project IDs.

For commands where it's possible, I think we should steer people away from using the org/project IDs. If we removed the flags, that would be a breaking change as previous command invocations would fail - I'm not sure if there is an easy way to have the field be accepted, but be ignored. At the very last, I think we could mark those fields as deprecated.
It could be that carrying those fields makes things more confusing than just removing them, in which case it could be justified to make a breaking change and remove them.

[stevensJourney]

It might make sense to deprecate these fields (and in SharedInstanceCommand).
We'd need to check how that gets displayed in the various command help sections. Ideally, users won't input this value for many commands anymore.

[LucDeCaf]

When using powersync pull instance --help, the --org-id and --project-id flags are marked with [Deprecated] in their message. Attempting to use the flags results in the following being printed to stderr (followed by whatever the command would have printed anyways):

 ›   Warning: --org-id is automatically resolved from --instance-id. This option currently remains as a manual override, but may be removed in a future version.
 ›   Warning: --project-id is automatically resolved from --instance-id. This option currently remains as a manual override, but may be removed in a future version.

[benitav]

I think we should steer people away from using the org/project IDs. If we removed the flags, that would be a breaking change as previous command invocations would fail - I'm not sure if there is an easy way to have the field be accepted, but be ignored.

Agreed, ideally they can just be ignored

[LucDeCaf]

Currently the CLI still accepts project-id and org-id and uses them as manual overrides (provided both are supplied). I think eventually we'll remove the options entirely in order to simplify the codebase (maybe a few versions down the line).