Remove done() call on SubMonitor in Refactoring

[vogella]

done() call not necessary here

See https://www.eclipse.org/articles/Article-Progress-Monitors/article.html

[github-actions]

Test Results

 1 214 files   -   607   1 214 suites   - 607   1h 12m 51s ⏱️ - 37m 57s
 7 726 tests ±    0   7 495 ✅  -     2  231 💤 +  3  0 ❌  - 1 
16 226 runs   - 8 113  15 713 ✅  - 7 878  513 💤  - 234  0 ❌  - 1 

Results for commit aaddfd6. ± Comparison against base commit 98ff2aa.

This pull request skips 3 tests.

UiTestSuite org.eclipse.ui.tests.api.ApiTestSuite org.eclipse.ui.tests.api.WorkbenchPluginTest ‑ testGetImageRegistryFromAdditionalDisplay
org.eclipse.jface.text.tests.contentassist.ContextInformationTest ‑ testContextInfo_hide_focusOut
org.eclipse.urischeme.internal.registration.TestUnitWinRegistry ‑ testWinRegistry

[jukzi]

The caller Will not expect that the callee invokes done() on the monitor. The caller must either use an SubMonitor (or a similar implementation which does not require done() to be invoked), or it must take responsibility for calling done() on the monitor after the callee has finished.
Reads like this done() is valid

[vogella]

The caller Will not expect that the callee invokes done() on the monitor. The caller must either use an SubMonitor (or a similar implementation which does not require done() to be invoked), or it must take responsibility for calling done() on the monitor after the callee has finished. Reads like this done() is valid

See Changes in Eclipse 4.7

See 5.3 Changes in Eclipse 4.7