TIKA-4704: add delete on exit in case delete fails

[THausherr]

Thanks for your contribution to Apache Tika! Your help is appreciated!

Before opening the pull request, please verify that

• there is an open issue on the Tika issue tracker which describes the problem or the improvement. We cannot accept pull requests without an issue because the change wouldn't be listed in the release notes.
• the issue ID (TIKA-XXXX)
  • is referenced in the title of the pull request
  • and placed in front of your commit messages surrounded by square brackets ([TIKA-XXXX] Issue or pull request title)
• commits are squashed into a single one (or few commits for larger changes)
• Tika is successfully built and unit tests pass by running ./mvnw clean test
• there should be no conflicts when merging the pull request branch into the recent main branch. If there are conflicts, please try to rebase the pull request branch on top of a freshly pulled main branch
• if you add new module that downstream users will depend upon add it to relevant group in tika-bom/pom.xml.

We will be able to faster integrate your pull request if these conditions are met. If you have any questions how to fix your problem or about using Tika in general, please sign up for the Tika mailing list. Thanks!

[Copilot]

Pull request overview

This PR addresses TIKA-4704 by ensuring the temporary bootstrap JAR created for forked parsing is scheduled for deletion at JVM shutdown if it can’t be deleted during ForkClient.close().

Changes:

• Register the fork bootstrap JAR for deleteOnExit() during ForkClient.close().

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

File#deleteOnExit() can throw SecurityException. Since close() currently doesn’t declare/expect to throw and is used in failure-cleanup paths, this new call can cause unexpected runtime failure during cleanup. Please guard the deleteOnExit() call (and any conditional logic around it) to keep close() best-effort.

Suggested change

	jar.deleteOnExit();
	try {
	jar.deleteOnExit();
	} catch (SecurityException ignore) {
	// best-effort cleanup; ignore inability to register deleteOnExit
	}

[THausherr]

There shouldn't be a SecurityException because it's our own file.