Batched Dependabot updates

[dependabot-batcher]

This PR was created by the Dependabot Batcher Action by combining the following PRs:

Wed Aug 02 2023

• Bump github.com/aws/aws-sdk-go-v2/service/glue from 1.54.0 to 1.59.1 #29934
• Bump github.com/fsouza/fake-gcs-server from 1.45.2 to 1.47.2 #29933
• Bump github.com/aws/aws-sdk-go-v2/feature/dynamodb/attributevalue from 1.10.30 to 1.10.35 #29932
• Bump github.com/aws/aws-sdk-go-v2/service/sqs from 1.23.4 to 1.24.1 #29927
• Bump github.com/aws/aws-sdk-go-v2/config from 1.18.30 to 1.18.32 in /assets/aws #29926
• Bump golang.org/x/net from 0.12.0 to 0.13.0 in /api #29924

Wed Aug 02 2023

• Bump github.com/jackc/pgconn from 1.14.0 to 1.14.1 #29942
• Bump cloud.google.com/go/container from 1.23.0 to 1.24.0 #29941
• Bump sigs.k8s.io/controller-tools from 0.12.0 to 0.12.1 #29939

[codingllama]

This might be breaking, although likely it's fine:

🐛 Change the type of markers.Collector.byPackage's key from string to *loader.Package by @​k8s-infra-cherrypick-robot in kubernetes-sigs/controller-tools#834

[codingllama]

tool.tsh.common.TestKube/list_kube variants are failing with errors similar to the one below:

Error:

"Kube Cluster Name Labels                                                                                                                                                                  Selected 
----------------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- -------- 
first-cluster     label1=val1 ultra_long_label_for_teleport_kubernetes_service_list_kube_clusters_method=ultra_long_label_value_for_teleport_kubernetes_service_list_kube_clusters_method          
root-cluster      label1=val1 ultra_long_label_for_teleport_kubernetes_service_list_kube_clusters_method=ultra_long_label_value_for_teleport_kubernetes_service_list_kube_clusters_method *        "

does not contain

"Kube Cluster Name Labels                                                                                                                                                                  Selected 
----------------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- -------- 
first-cluster     label1=val1 ultra_long_label_for_teleport_kubernetes_service_list_kube_clusters_method=ultra_long_label_value_for_teleport_kubernetes_service_list_kube_clusters_method          
root-cluster      label1=val1 ultra_long_label_for_teleport_kubernetes_service_list_kube_clusters_method=ultra_long_label_value_for_teleport_kubernetes_service_list_kube_clusters_method          "

Notice the * in the "Selected" column:

  Kube Cluster Name Labels                                                                                                                                                                  Selected
  ----------------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- --------
  first-cluster     label1=val1 ultra_long_label_for_teleport_kubernetes_service_list_kube_clusters_method=ultra_long_label_value_for_teleport_kubernetes_service_list_kube_clusters_method         
- root-cluster      label1=val1 ultra_long_label_for_teleport_kubernetes_service_list_kube_clusters_method=ultra_long_label_value_for_teleport_kubernetes_service_list_kube_clusters_method *       
+ root-cluster      label1=val1 ultra_long_label_for_teleport_kubernetes_service_list_kube_clusters_method=ultra_long_label_value_for_teleport_kubernetes_service_list_kube_clusters_method         

I think that's alright, as in we can fix the test and move on, but copying @tigrato for confirmation.

[codingllama]

PTAL @rosstimothy @tigrato, especially at the changed kube test.

[tigrato]

@codingllama

I think this * thing is a concurrency issue from other tests.
tsh kube ls decides the selected if the default kubeconfig $HOME/.kube/config or the value from $KUBECONFIGenv var has that cluster in the current-context.

listKube test shouldn't have the selected values. I will take a look

[codingllama]

Thanks, @tigrato. Feel free to commit to this PR.

[codingllama]

Alternatively we can rollback the k8s changes, let me give that a try. It may be for the best.

[codingllama]

Actually, I'm seeing failures in other PRs, so this may have nothing to do with the version updates. I'll drop the test changes and I think we should follow up with a fix in a separate PR.