Initial user token has DB-wide access, but only appears under 1st org in the UI

**Steps to reproduce:**
List the minimal actions needed to reproduce the behavior.

1. Set up a fresh OSS 2.x instance in the UI, creating a baseline `org_a` and `superuser`
2. Create a 2nd org `org_b` in the UI
3. Navigate to `Data` -> `Tokens` under `org_a`
4. Navigate to `Data` -> `Tokens` under `org_b` (and refresh the page, see #406)

**Expected behavior:**
Either:
* `superuser`'s token appears under both `org_a` and `org_b`, because it has all-access power to both
* `superuser`'s token appears under neither `org_a` nor `org_b`, because it's a special type of token created via the onboarding process

**Actual behavior:**
`superuser`'s token appears under `org_a`, but not `org_b`. This mismatch led a user to believe cross-org auth was broken when they were able to use a token from `org_a` to write data into a bucket under `org_b` (see influxdata/idpe#9372)