TCK enhancement poll for task completion instead of sleeping

[KyleAure]

Currently, there are a number of tests that will use Thread.sleep() to pause execution to wait for task completion.
During the TCK port I centralized this activity to a single point for future enhancement:

concurrency/tck/src/main/java/ee/jakarta/tck/concurrent/framework/TestUtil.java

Lines 167 to 180 in cc64ec4

	/**
	* USE WITH CAUTION!!
	* When possible tests should use waitFor methods to wait for specific condition to be meet.
	* Pausing the thread for a specific duration will directly impact test performance but in some cases is required.
	*
	* Pauses the calling thread for the specified duration
	*
	* @param duration - duration to sleep
	* @throws InterruptedException
	*/
	public static void sleep(Duration duration) throws InterruptedException {
	log.config("Sleeping " + duration.toMillis() + " milliseconds");
	Thread.sleep(duration.toMillis());
	}

Instead of sleeping the thread, we should instead use the already available waitForXXX() methods that exist in the test utility.
Or for cases when we are going down an error path and need to wait for something to expire, we should perform polling to either fail, or succeed as quickly as possible.

There are instances where polling is already performed and the poll interval and duration are standardized to a constant here:

concurrency/tck/src/main/java/ee/jakarta/tck/concurrent/framework/TestConstants.java

Lines 33 to 38 in cc64ec4

	//Durations
	/** 1 second */
	public static final Duration PollInterval = Duration.ofSeconds(1);
	/** 15 seconds */
	public static final Duration WaitTimeout = Duration.ofSeconds(15);

Consider introducing system properties to allow for implementations to specify their own interval and duration.

[KyleAure]

I've standardized this behavior whenever possible in the TCK. There are now only a few required places were we need to sleep to verify behavior.