* feat(seeding): seed accounts and pods with seeded-pod-config.json
* feat(seeding): dry up SeededPodInitializer by using RegistrationManager directly and make compatible with version/3.0.0
* feat(seeding): update seed config files to version 3.0.0 context
* feat(seeding): simplify seeded-root config by importing pre-existing prefilled-root config
* feat(seeding): Add seeding as a default initializer, update seeded pod copy and guide, change seeded pod config to array
* feat(seeding): remove template info from seeded pod guide, use mockFs, code style nit, fix redlock test
* feat(seeding): remove old config file
* feat: (AppRunner) Mechanism to configure cli args and derive componentsjs vars from them implemented
* fix: (AppRunner) tidying
* fix: (AppRunner) tidying up
* fix: (AppRunner) runCli method made sync
* fix; (VarResolver) refactored to multiple files, and other stylistic fixes.
* chore: (AppRunner) Uses builder pattern for yargs base arguments setup to enable better typescript inference
* fix(AppRunner): refactoring AppRunner and VarResolver
* fix(AppRunner): refactoring AppRunner promise handling
* fix(AppRunner): verror dependency removal
* fix: Simplify CLI error handling
* feat: Use same config for both CLI and app instantiation
* fix: Update typings and imports
* feat: Split VariableResolver behaviour to 2 classes
* feat: Move default value behaviour from CLI to ValueComputers
* test: Add unit tests for new CLI classes
* feat: Integrate new CLI configuration with all default configurations
* feat: Add createApp function to AppRunner
* docs: Update comments in CLI-related classes
* fix: Various fixes and refactors
Co-authored-by: damooo <damodara@protonmail.com>
The initializer can now be used for any container.
The initializer also does not handle the repeat check anymore,
this is now configured with a ConditionalHandler.
This allows easier reuse of certain reoccurring behaviours,
such as authorization.
The AuthenticatedLdpHandler is no longer required
since it is a combination of parsing and authorization.
This did require a small change to the OperationHandler interface.
This adds options for enabling setup to the config folder.
All default configs with permanent storage (file/sparql)
are configured to require setup at server start.
Memory-based configs merely have it as an option.
