test: skip 8 integration tests broken by test-org fixture drift

[riyazsh]

Summary

Marks 8 integration tests as `@pytest.mark.skip` — they have been failing consistently on scheduled `main` runs for the past several days due to test-org fixture drift, not code regressions.

Failing tests + root causes

File	Test	Reason
`test_logs_archives.py`	`test_resource_sync`	Test-org archive references a missing S3 bucket → sync fails with `400 Bad Request - Bucket does not exist on AWS S3`
`test_logs_archives.py`	`test_resource_sync_per_file`	Same
`test_logs_archives.py`	`test_resource_update_sync`	Same
`test_logs_archives.py`	`test_resource_update_sync_per_file`	Same
`test_logs_archives_order.py`	`test_resource_sync`	Depends on logs_archives sync (skipped above)
`test_logs_archives_order.py`	`test_resource_sync_per_file`	Same
`test_metric_tag_configurations.py`	`test_resource_import`	Test org has no metric_tag_configurations to import → `AssertionError: No individual files found`
`test_metric_tag_configurations.py`	`test_resource_import_per_file`	Same

Evidence

• Scheduled `main` run 2026-07-06: 28776343791 — same 8 tests fail
• Scheduled `main` run 2026-07-05: 28733357023 — same
• Scheduled `main` run 2026-07-03: 28645448265 — same
• Scheduled `main` run 2026-07-02: 28573142710 — same
• Bucket-missing error, exact log line from CI:
  ```
  ERROR datadog_sync_cli [logs_archives - 4n70c12NSSOIa5fhDTUCNg]
  400 Bad Request - {"errors":["Bucket does not exist on AWS S3"]}
  ```

Approach

Extends the existing `@pytest.mark.skip` pattern already used in these files (e.g. `test_logs_archives.py` already skips `test_resource_import*` with reason "require an AWS, GCP, or Azure account"). Skip reasons here call out the specific test-org fixture problem so the tests can be unskipped once fixtures are restored.

Why now

Unblocks the `test-integrations` check for all in-flight PRs (e.g. #602). No test coverage lost — these tests weren't providing signal anyway; they've been failing every run for 4+ days.

Test plan

• CI green (all remaining tests still run and pass)
• Follow up: restore the S3 bucket fixture on the test org and un-skip; provision a metric_tag_configuration on the source org and un-skip