chore(3000): Remove organization from breadcrumbs

[Twixes]

Changes

I propose we introduce the following split in 3000: organization switching lives in the account popover, while project switching lives in breadcrumbs. Currently you can do the former from breadcrumbs AND the popover, while the latter ONLY from breadcrumbs. I'm not sure that this is entirely good for the discoverability of projects, but I definitely think that it's redundant for orgs.

To this end, this PR removes the organization breadcrumb in 3000.

[posthog-bot]

📸 UI snapshots have been updated

179 snapshot changes in total. 0 added, 179 modified, 0 deleted:

• chromium: 0 added, 125 modified, 0 deleted (diff for shard 1, diff for shard 2)
• webkit: 0 added, 54 modified, 0 deleted (diff for shard 2)

Triggered by this commit.

👉 Review this PR's diff of snapshots.

[github-actions]

Size Change: +51 B (0%)

Total Size: 1.99 MB

ℹ️ View Unchanged

Filename	Size	Change
frontend/dist/toolbar.js	1.99 MB	+51 B (0%)

_{compressed-size-action}

[daibhin]

Looks like the pre-3000 UI is also affected when the code suggests that it shouldn't be?

[thmsobrmlr]

I initially thought this is a great idea - people likely don't switch the organization much and this simplifies the UI. Unexpectedly the org switcher seems to be used quite a bunch by users though https://app.posthog.com/data-management/actions/59306 (given I've not made a mistake setting up the action).

[Twixes]

Hmm, that's interesting @thmsobrmlr! Yeah, it does look like the org switcher has a bit over 1/3 of the project switcher's DAUs in 3000 – which is a big chunk, because project switching is not even available elsewhere. Though also interesting, because I would suspect A LOT more users to be multi-project rather than multi-org.
New organizations are created from breadcrumbs more than from the account popover.
(Insight for both analyses.)
So let's say we keep the organization in breadcrumbs.

[corywatilo]

I've actually been using the breadcrumb a ton to switch orgs! Ultimately I think it should move to the nav column (likely at the top) as this turned out to be a pretty good solution for a company that rhymes with Leap. But what we have works for now and definitely helps keep all the controls in one place and prevents thrash of what to expect where.

Now if only we can clear up the ambiguity between project settings, personal settings, and billing...