Replace requirejs optimizer with webpack

[bd82]

Initial Productive Version / Technical viability

• Research
• entryPoint adapter Generation.
• Define & Expose default config.
• Option to choose requirejs/webpack (default is requirejs)
• Collect services and commands for use as nested entry points.
• Should any other resources be collected as nested entry points? (tips/plugin.json module?)
• How (should?) to handle UI5 loader plugin used inside WebIDE?
• Minor bug - a webpack error would result in the generated entry point not being deleted.
• Bug running under windows

Initial version has been implemented and merged.
next topics for productization.

Adoption & Productization

• Integrate into a productive plugin 1
• Integrate into a productive plugin 2
• Integrate into a productive plugin 3 (?)
• Define as default bundler.
• Use in feature example.
• Update Docs (?)

Additional capabilities (future)

• Ability for end user to expose additional amd modules.

Optimizations (Future)

• Investigate bundling CSS with JS artifact using standard webpack plugins.
• Investigate bundling svg (storyboard) with JS artifact using standard webpack plugins.
• Bundle I18N with JS artifact using custom logic (add to generated entry point).

Deprecation of requirejs usage.

• Remove requirejs optimizer.

  • Source Code.
  • package.json depedency
  • Hacks related for running require.js inside jest.

• Update ChangeLog and mini migration guide (e.g what is expected to break / need adjustments...)

[bd82]

#24