Add basic code mining tracing option to trace rendering

[iloveeclipse]

See #2786

[iloveeclipse]

@mickaelistria, @tobiasmelcher : WDYT? At least some basic data?

[mickaelistria]

I don't think it's so relevant to add this in the code; adding those as conditional breakpoints when needed is easy enough IMO.

[iloveeclipse]

I was thinking about people who don't have SDK sources checked out - these options are tracing options everyone can set at runtime.

[github-actions]

Test Results

 1 214 files   -   607   1 214 suites   - 607   1h 7m 23s ⏱️ - 20m 30s
 7 723 tests ±    0   7 490 ✅  -     5  233 💤 +  5  0 ❌ ±0 
16 220 runs   - 8 110  15 705 ✅  - 7 876  515 💤  - 234  0 ❌ ±0 

Results for commit e2ac351. ± Comparison against base commit c9f129d.

This pull request skips 5 tests.

org.eclipse.ui.genericeditor.tests.HoverTest ‑ testEnabledWhenHover
org.eclipse.ui.genericeditor.tests.HoverTest ‑ testMultipleHover
org.eclipse.ui.genericeditor.tests.HoverTest ‑ testProblemHover
org.eclipse.ui.genericeditor.tests.HoverTest ‑ testSingleHover
org.eclipse.ui.genericeditor.tests.ShowInformationTest ‑ testInformationControl