infopack "stand alone" mode should be opt-in in next major release

The current standard (1.*) requires html files to be generated with every pipeline run. The purpose of this was to be able to "browse the content" as a static website in for example a folder on the hard drive and to enable "serverless" browsing in storage.

Some problems with this approach:

1. Added complexity in the infopack
2. HTML files might become obsolete over time and might stop work as the web standards develops further. (infopack output should never be altered since its considered a release)

Proposed solution:

1. meta.html files and the index.html should be considered opt-in (stand alone mode)
2. The registry must be able to parse and render html dynamically files from the meta.json files instead