8343101: Rework BasicTest.testTemp test cases

[GoeLin]

I backport this for parity with 17.0.15-oracle.

This is based on the commit to 21. I needed to resolve again, though:
https://bugs.openjdk.org/browse/JDK-8291978: jpackage: allow to override primary l10n files on Windows is not in 17.

I include some of the edits of 8291978 in this change, as they nicely clean up the test code.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• JDK-8343101 needs maintainer approval
• JDK-8343178 needs maintainer approval
• Commit message must refer to an issue

Issues

• JDK-8343101: Rework BasicTest.testTemp test cases (Enhancement - P4 - Requested)
• JDK-8343178: Test BasicTest.java javac compile fails cannot find symbol (Bug - P3 - Requested)

Reviewers

• Martin Doerr (@TheRealMDoerr - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk17u-dev.git pull/3176/head:pull/3176
$ git checkout pull/3176

Update a local copy of the PR:
$ git checkout pull/3176
$ git pull https://git.openjdk.org/jdk17u-dev.git pull/3176/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 3176

View PR using the GUI difftool:
$ git pr show -t 3176

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk17u-dev/pull/3176.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back goetz! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

❗ This change is not yet ready to be integrated.
See the Progress checklist in the description for automated requirements.

[openjdk]

This backport pull request has now been updated with issues from the original commit.

[mlbridge]

Webrevs

• 00: Full (f6dc7873)

[TheRealMDoerr]

LGTM.

[openjdk]

⚠️ @GoeLin This change is now ready for you to apply for maintainer approval. This can be done directly in each associated issue or by using the /approval command.