Enable logging in Eclipse Platform and Eclipse SDK products

[jonahgraham]

In 4.28 a lot of work was done to enable slf4j in #588 and related issues, leading to this entry in the the N&N:

Migrate to SLF4J-2 from Maven-Central

Besides breaking changes in the other sfl4j packages than org.sfl4j, version 2 has also changed the way to connect the slf4j.api bundle to a logging-backend to use Java's ServiceLoader mechanism. Consequently you have to make sure that the logging-backend used in your application uses is compatible with slf4j.api version 2. Additionally a OSGi Service Loader Mediator is needed to permit Java's ServiceLoader access to the the provider bundle. To fulfill this requirement Eclipse Platform ships org.apache.aries.spifly.dynamic.bundle by default. If you assemble a final application you have to ensure that this bundle is automatically activated during startup. For an Eclipse Product this can be achieved by assigning the Plug-in org.apache.aries.spifly.dynamic.bundle a suitable start-level in the Configuration section of your product.

This issue to to apply those changes to the Eclipse Platform and Eclipse SDK products.

This issue came out of discussions in EPP eclipse-packaging/packages#27 and EPP will adapt the packages in the same way as platform.

I am not sure if it should be covered under the same issue, or a separate issue, but making the default logger in Eclipse log to the Eclipse .log rather than no-op logging may be best?