Flaky test fix TestCanGetKeyspaces

[GuptaManan100]

Description

This PR further fixes more flakiness in TestCanGetKeyspaces. It was noticed in the CI -

I0618 04:44:44.442798   13689 main.go:332] Local cluster started.
main_test.go:467:
Error Trace:	/opt/actions-runner/_work/vitess/vitess/go/cmd/vttestserver/cli/main_test.go:467
/opt/actions-runner/_work/vitess/vitess/go/cmd/vttestserver/cli/main_test.go:254
Error:      	Received unexpected error:
rpc error: code = DeadlineExceeded desc = context deadline exceeded
Test:       	TestCanGetKeyspaces

The problem was that we created a context with timeout in the start before the cluster was setup. The cluster setup can take more than 10 seconds, especially in the CI. So, we should be creating the context after the cluster setup is complete.

Related Issue(s)

Checklist

• "Backport to:" labels have been added if this change should be back-ported to release branches
• If this change is to be back-ported to previous releases, a justification is included in the PR description
• Tests were added or are not required
• Did the new or modified tests pass consistently locally and on CI?
• Documentation was added or is not required

Deployment Notes

[vitess-bot]

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

• Ensure that the Pull Request has a descriptive title.
• Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

• Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

• Apply the release notes (needs details) label if users need to know about this change.
• New features should be documented.
• There should be some code comments as to why things are implemented the way they are.
• There should be a comment at the top of each new or modified test to explain what the test does.

New flags

• Is this flag really necessary?
• Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

• Each item in Jobs should be named in order to mark it as required.
• If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

• Protobuf changes should be wire-compatible.
• Changes to _vt tables and RPCs need to be backward compatible.
• RPC changes should be compatible with vitess-operator
• If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
• vtctl command output order should be stable and awk-able.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.56%. Comparing base (231ba6b) to head (a820177).

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #16214   +/-   ##
=======================================
  Coverage   68.55%   68.56%           
=======================================
  Files        1544     1544           
  Lines      197895   197895           
=======================================
+ Hits       135672   135691   +19     
+ Misses      62223    62204   -19     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.