[Antithesis] Rename DATA_PATH as prefix

[nwnt]

As discussed in the community call, I'm breaking the previous PR down to smaller steps. This is the first of the series.

@serathius

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.11%. Comparing base (2261dfb) to head (aac05ad).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

see 21 files with indirect coverage changes

@@            Coverage Diff             @@
##             main   #20781      +/-   ##
==========================================
- Coverage   69.20%   69.11%   -0.10%     
==========================================
  Files         422      422              
  Lines       34821    34821              
==========================================
- Hits        24099    24067      -32     
- Misses       9325     9354      +29     
- Partials     1397     1400       +3     

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2261dfb...aac05ad. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[nwnt]

The verification fails due to mismatched go versions in go.mod and go.work. See the above PR.

[serathius]

Please avoid such changes mixed into unrelated PRs.

[nwnt]

Sorry didn't see these and was focusing on what broke the changes. These came from the auto linters I have, but all are reverted.

[serathius]

/retest

[k8s-ci-robot]

@nwnt: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-etcd-unit-test-arm64	aac05ad	link	true	/test pull-etcd-unit-test-arm64

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nwnt, serathius

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 [serathius]

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