Bump version of org.eclipse.swt.svg for JSVG dependency update

[HeikoKlare]

The JSVG dependencies have been updated to a new minor version including an explicit setup of the logging with OSGi capabilities. To properly reflect this change in dependencies, this bumps the version of the SWT SVG fragment to the next minor version.

Follow-up to:

• Update jsvg to 2.1.0 in org.eclipse.swt.svg #3283

@merks in my opinion this better reflects the "complexity" of the dependency change. What do you think?

[merks]

I guess we often update dependencies without incrementing the places that use them, but I think in this case it's probably a good idea. We did actually change the lower bounds, so that's a significantly visible change if not an actual API addition. In any case, it most definitely won't hurt and it better helps to identify the boundary.

[HeikoKlare]

Thank you for the clarification. Yes, a dependency update does usually not mean that we bump the version of its consumers in the same way. This is just a case-specific proposal for a version bump upon a dependency update, motivated by what you have explained.

[github-actions]

Test Results

  182 files  ±0    182 suites  ±0   27m 32s ⏱️ +41s
4 723 tests ±0  4 700 ✅ ±0   23 💤 ±0  0 ❌ ±0 
6 812 runs  ±0  6 649 ✅ ±0  163 💤 ±0  0 ❌ ±0 

Results for commit 95c0624. ± Comparison against base commit d63140f.