Increase external test pod start timeout

[torredil]

What is this PR about? / Why do we need it?

Recently, our CI has been consistently failing due to testing pods taking longer than 5 minutes (default) to transition into a running state. See #1578 as an example.

This PR increases the pod start timeout when running the external storage tests by modifying the DriverDefinitionTimeouts.PodStart parameter:

// Timeouts contains the custom timeouts used during the test execution.
// The values specified here will override the default values specified in
// the framework.TimeoutContext struct.
Timeouts map[string]string

What testing is done?

• CI
• Stress testing

  StressTestOptions:
    NumPods: 10
    NumRestarts: 10

kubetest2 noop \                                                                          
  --run-id="e2e-kubernetes" \
  --test=ginkgo \
  -- \
  --test-package-version=v1.27.0-alpha.3 \
  --skip-regex="\[Disruptive\]" \
  --focus-regex="\bebs.csi.aws.com\b.*multiple pods should access different volumes repeatedly" \
  --parallel=15 \
  --test-args="-storage.testdriver=manifests.yaml"

[rdpsin]

/lgtm

[rdpsin]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rdpsin

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rdpsin]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment