release-22.2: backupccl: speed up listing in some backup callsites

[blathers-crl]

Backport 1/1 commits from #93072 on behalf of @adityamaru.

/cc @cockroachdb/release

---

There were a couple of calls to List that would list all the files in the backup destination bucket. In the presence of a large number of files, usually SST files in the data/ folder, this listing could be very slow. This could manifest as a RESTORE command hanging during the planning phase when we go to resolve encryption information from the base backup bucket.

To fix this, we add a delimiter to the List call that will make skipping over all files in the data/ directory much cheaper.

Informs: https://github.com/cockroachlabs/support/issues/1937

Release note (bug fix): speedup slow listing calls that could manifest as restore queries hanging during execution, in the presence of several backup files

---

Release justification: low risk change with high impact for customers restoring from buckets with a large number of files

[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