Perform initial work in the job

[laeubi]

Currently the first thing a reconciler after startup does is to sleep for a while then call initialProcess then start the processing loop (that sleeps again...).

This now moves this initial work into the start job so we have a plain processing loop in the thread to make further improvements easier.

[github-actions]

Test Results

 2 778 files  ±0   2 778 suites  ±0   1h 38m 47s ⏱️ + 5m 11s
 7 930 tests ±0   7 700 ✅  - 2  228 💤 ±0  2 ❌ +2 
23 345 runs  ±0  22 597 ✅  - 2  746 💤 ±0  2 ❌ +2 

For more details on these failures, see this check.

Results for commit f46fb35. ± Comparison against base commit f41ea06.

♻️ This comment has been updated with latest results.

[iloveeclipse]

I'm not sure if that change would not break the implementation of existing clients, the code is very old to there is ahigh probability someone extended it.

BackgroundThread.run() javadoc says that it will call initialProcess() and that was always done in the BackgroundThread. Now with this change the code will run in a different thread.

[laeubi]

BackgroundThread.run() javadoc says that it will call initialProcess() and that was always done in the BackgroundThread. Now with this change the code will run in a different thread.

I think that is more it run in a background thread than in the BackgroundThread ... to prevent confusion I renamed that class now and don't let it implement Thread but instead creating one. I also adjuste the code so anyone that needs to know that it is inside the reconcile background thread can still query it using AbstractReconciler.isRunningInReconcilerThread() that is the only place an implementation can actually hook in / extend anything.