Add test for non-default time zones on Windows

[jefferbrecht]

Description

Add test for non-default time zones on Windows, which is currently broken. When fluent-bit is fixed upstream, merge the fix here and re-run the tests.

Related issues

b/218888265
fluent/fluent-bit#2941

How has this been tested?

Ran tests locally; will let the standard tests run in the PR.

Checklist:

• Unit tests
  • Unit tests do not apply.
  • Unit tests have been added/modified and passed for this PR.
• Integration tests
  • Integration tests do not apply.
  • Integration tests have been added/modified.
• Documentation
  • This PR introduces no user visible changes.
  • This PR introduces user visible changes and the corresponding documentation change has been made.
• Minor version bump
  • This PR introduces no new features.
  • This PR introduces new features, and there is a separate PR to bump the minor version since the last release already.
  • This PR bumps the version.

[sophieyfang]

What if the new windows VM default time zone is just the same as Eastern Time. Does the VM created with zone us-east1 default to have Eastern Time?

[jefferbrecht]

If the default time zone is already Eastern Time then this command is a no-op and the test should still fail as expected.

In my testing the VM time zone was always UTC regardless of which Cloud zone it was created in.

[franciscovalentecastro]

Should we update also TestCustomLogFormat in this PR too ? Since it uses UTC to avoid hitting the timezone bug.

ops-agent/integration_test/ops_agent_test.go

Lines 837 to 844 in 3ec1e25

	// When not using UTC timestamps, the parsing with "%Y-%m-%dT%H:%M:%S.%L%z" doesn't work
	// correctly in windows (b/218888265).
	line := fmt.Sprintf("<13>1 %s %s my_app_id - - - qqqqrrrr\n", time.Now().UTC().Format(time.RFC3339Nano), vm.Name)
	if err := gce.UploadContent(ctx, logger, vm, strings.NewReader(line), logPath); err != nil {
	t.Fatalf("error writing dummy log line: %v", err)
	}

[jefferbrecht]

Closing because this has been moved into #1078.