chore: log an info message before polling upstream for data

Ensures that we don't trigger CircleCI's "kill job because it didn't output anything" timeout, and gives us some visibility into how long it takes for a workload to appear in the upstream.

Author: ivanstanev

test/helpers/kubernetes-upstream.ts

@@ -25,6 +25,7 @@ export async function validateUpstreamStoredData(
   remainingChecks: number = maxPodChecks,
 ): Promise<boolean> {
   while (remainingChecks > 0) {
+    console.log(`Pinging upstream for existing data (${remainingChecks} checks remaining)...`);
     const responseBody = await getUpstreamResponseBody(relativeUrl);
     const workloads: IWorkloadLocator[] | undefined = responseBody.workloads;
     const result = validatorFn(workloads);
@@ -43,6 +44,7 @@ export async function validateUpstreamStoredMetadata(
   remainingChecks: number = maxPodChecks,
 ): Promise<boolean> {
   while (remainingChecks > 0) {
+    console.log(`Pinging upstream for existing metadata (${remainingChecks} checks remaining)...`);
     const responseBody = await getUpstreamResponseBody(relativeUrl);
     const workloadInfo: IWorkloadMetadata | undefined =
       responseBody.workloadInfo;