release-22.2: tenant: add support to Log endpoints to status server

[jeffswenson]

Backport 1/1 commits from #91604.

/cc @cockroachdb/release

Release justification: Including logs in debug zips simplifies debugging issues in multi-tenant deploys.

---

Previously, the tenant status server did not support the log-file related
endpoints leading to missing logs in the debug.zip when generating for a tenant
server.

This commit migrates the implementations from the standard status server into
the tenant, adjusts for fanout to instances instead of nodes, and leaves the
rest as-is.

Resolves: #91992
Epic: CC-5168

Release note (ops change): generating a debug.zip for a tenant server will now
include logs in the zip file.

[blathers-crl]

Thanks for opening a backport.

Please check the backport criteria before merging:

• Patches should only be created for serious issues or test-only changes.
• Patches should not break backwards-compatibility.
• Patches should change as little code as possible.
• Patches should not change on-disk formats or node communication protocols.
• Patches should not add new functionality.
• Patches must not add, edit, or otherwise modify cluster versions; or add version gates.

If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.

• There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
• The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
• New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
• The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

• What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
• Will this work in a cluster of mixed patch versions? Did we test that?
• If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

[cockroach-teamcity]

This change is 

[jeffswenson]

-       instance, err := t.sqlServer.sqlInstanceReader.GetInstance(ctx, instanceID)
+       instance, err := t.sqlServer.sqlInstanceProvider.GetInstance(ctx, instanceID)

I made a small change to get the patch to build on 22.2. sqlInstanceProvider was renamed to sqlInstanceReader.

[dhartunian]

I made a small change to get the patch to build on 22.2. sqlInstanceProvider was renamed to sqlInstanceReader.

👍

Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @jeffswenson)

---

pkg/cli/testdata/zip/testzip_tenant line 144 at r1 (raw file):

[node 1] 0 goroutine dumps found
[node 1] requesting log file ...
[node 1] 0 log file ...

I'm surprised this test didn't have to change on the original PR. Do you know why?

[jeffswenson]

pkg/cli/testdata/zip/testzip_tenant line 144 at r1 (raw file):

[node 1] 0 goroutine dumps found
[node 1] requesting log file ...
[node 1] 0 log file ...

I'm surprised this test didn't have to change on the original PR. Do you know why?

It looks like the test is skipped:

cockroach/pkg/cli/zip_tenant_test.go

Line 34 in 5f310bc

skip.WithIssue(t, 89192, "flaky test")