Ember dandi integration with OSB

[D-GopalKrishna]

Task description:
Researchers upload their data to EMBER-DANDI instead of the public bucket, and the
analysis runs on it in OSB as before. Each run ends with a DOI for their data.

• Two logins (EMBER-DANDI and OSB) from one Login dialog; uploading needs both.
  EMBER login opens in a popup. One Logout signs out of both. Users are assumed to
  have an approved EMBER account already (EMBER has its own approval process).
• Upload to EMBER-DANDI: into the researcher's own dandiset (picked or created per
  protocol), and optionally a copy into the protocol's MAABCD dandiset ("Share a copy of
  this data with the MAABCD consortium", on by default) through OSB's new /ember
  endpoints. OSB imports the researcher's copy into the workspace and runs the notebooks.
• Dandiset metadata records the protocol and the OSB workspace (EMBER's "Related
  resources"), so choosing a protocol offers the researcher's dandisets with their workspaces.
• DOI: once the notebooks pass, the researcher's dandiset is published as a new
  version; the dialog shows its DOI with Copy. The MAABCD dandiset is never published.
• Retry carries on where a run stopped (no re-upload, same workspace and run folder),
  and closing the dialog doesn't lose a run in progress.
• Also: "My dandisets" link in the header, Protocols page's Data upload button, OSB shown as
  logged in only while it has a token, visible disabled buttons, comment tidy-up.

---

Screenshots of some of the changes:

The two upload looks like (continuing to keep one logout - which will logout from both)

Login with Ember looks like this for the first time. (We assume user has a ember account - there's no signup process here for Ember like OSB - since Ember needs an approval process - which is something user is expected to do in ember official website)

Notice the Related resources section in Ember Dandiset - it takes it from the metadata coming from the upload.

One can continue from where it failed - so if one of the steps got failed - retry continues from where it failed.

Selecting the same Ember dandiset will show up something like below - since you have published previosuly and new upload does a new publishing to give you new DOI from the same Dandiset.

[D-GopalKrishna]

Left for dev environment to be tested fully:

• EMBER: a consortium account with one MAABCD dandiset per protocol, and its API key.
• OSB Keycloak: user maabcd-consortium with attribute EMBER_API_KEY (admin-only attributes).
• OSB: deploy workspaces with the /ember endpoints.
• IDP: an EMBER OAuth app (redirect https://<IDP domain>/ember-callback) → VITE_EMBER_CLIENT_ID;
  real maabcdDandisetIds in protocols.json; confirm the license (CC-BY-4.0 for now).