Docforge v1 - fully reproducible website bundles from a docforge config and manifest file

[Kostov6]

What would you like to be added:
Code that makes website bundles fully reproducible without dependency on where docforge is being run. This enables local builds to fully reproduce the deployed website bundle

Why is this needed / describe a real-world scenario:

The main improvements we would like to achieve with docforge v1:

• future website features are added as quickly and easily as possible with high confidence
• future website features are encoded into the build configuration. This makes them trivially reusable
• reduce maintenance cost as much as possible by
  • ensure future changes don't introduce unexpected changes to gardener/website
  • unit test important components
  • easily reproduce and debug faulty build configurations

Those improvements will be reached by achieving the following goals:

• introduce core package having as little dependencies as possible. It will explicitly define the surface area of the core docforge logic through interfaces
• introduce core/plugin/interface.go that will be implemented by plugins stored in plugins/<name>
• split current logic into a md,download,persona,hugo,docsy plugins
• improve documentation

How to categorize this?:

/kind enhancement
/priority 3