feat: update b2b sso organization documentation

[jonas-jonas]

Related Issue or Design Document

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

[jonas-jonas]

Don't merge, it's not live yet.

[vinckr]

Its live now right @jonas-jonas ?

Btw do you think it makes sense to keep the example how to configure it via API in, or was that more hacky than it should be?

[jonas-jonas]

Ah, yes, it is.

The API example is really hacky, and we shouldn't have that in the documentation, IMO. The CLI will support it soon (ish): ory/cli#318

But since it doesn't support it yet, might be good to keep the API example in there... I guess I'll revert the removal for now.

[vinckr]

I guess I'll revert the removal for now.

Your call 😁
IMO if there are concrete plans to add it to the CLI, we can remove it.
I dont see too many users using it in that way tbh.
But if the CLI/API plans are still a longer time out (say Q1'24) then I would leave it in.

[jonas-jonas]

Then let's merge. @hperl said he's working on the CLI PR still, but should be available soon.