[bug/FR]: Data Explorer loads measurements for first sorted bucket always

## About the bug

When you visit the Data Explorer page `orgs//data-explorer`, it automatically loads the measurements for the first sorted bucket. If i'm an enterprise customer, I likely have many buckets and the the chance the first one is the one i want to use is `1/n` which approaches zero. Because the sort order is not controllable (it appears to be alphanumeric but systems buckets sorted last), I can't _put_ the most important bucket first.

Executing the query to get the measurements is a billable query - thus usually an excess query that I can't avoid as a customer if i want to use the Data Explorer. In other situations and pages, I click a submit button to run the query knowing I'll be billed.

Lastly, the first sorted bucket could be a really big bucket where getting the measurement list might take seconds, delaying my use of the data explorer.

I marked this as a bug because of "excess" query execution, but I could also see it being called a FR. This is a small behavior change for a slightly larger benefit so I think it has a good ratio of effort to rewards.

If we have 10k customers and every customer visits the data explorer each day (as we hope) and for most the first bucket isn't the right one, influx will save having to execute ~3 million queries a year that absorb real compute resources but don't provide value to the customer.

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

1. visit the data explorer
2. see that the first sort bucket has it's measurements loaded

**Expected behavior:**

Visiting the data explorer does not issue a measurement tags query until I select a bucket in the first picker.

**Actual behavior:**

The measurements of the first sorted bucket are queried for.

**Visual Proof:**

contrived RL example:

## About your environment

**Environment info:**
cloud2

**Config:**

na

**Logs:**

na
**Performance:**
na