Detect preload format from minVersion in manifest.json (or version of sap.ui.core dependency)

Expected Behavior

Especially for applications the preload format should be detected from the minVersion property in the manifest.json. This ensures that even if newer versions for the dependencies (also most important the dependency to sap.ui.core) are used the Component-preload is created in the proper expected format. This is also how the Grunt tooling worked.

For libraries, being built today it should work when using the proper dependency to an older version of the sap.ui.core library.

Current Behavior

Today, the BundleBuilder (from LBT) decides depending on the existence of the ui5loader whether this should be a EVOBundleFormat (sap.ui.require.preload) or a UI5BundleFormat (jQuery.sap.registerPreloadedModules).

As soon as we support manifest-first for libraries the same like for components should also apply as the minVersion can then also be defined in the manifest.json. Today, the minVersion is derived from the sap.ui.core library dependency.

Context

• UI5 Module Version (output of ui5 --version when using the CLI): 1.5.2
• Node.js Version: not relevant
• npm Version: not relevant
• OS/Platform: not relevant

Affected components (if known)

• ui5-builder
• ui5-server
• ui5-cli
• ui5-fs
• ui5-project
• ui5-logger

Start in the ui5-builder component, focusing on the BundleBuilder and its current EVOBundleFormat/UI5BundleFormat selection. Review how minVersion is read from manifest.json and how the sap.ui.core dependency is used for libraries. Done means preload format selection follows the applicable minVersion for applications and libraries, with coverage for both sources.