add dummy rule for duckdb installs

[irm-codebase]

Fixes #60

Summary of changes in this pull request

• Added a dummy rule with a core: 1 limit to avoid the parallel race condition caused by duckDB's plug in approach.

This does not fix the problem if multiple instances of the module are imported, unfortunately. The new scenarios approach diminishes the need for that, though.

Reviewer checklist

• There are no pip dependencies in the module's environment files (workflow/envs/).
• All rules use pathvars (e.g., <results>) in their inputs and outputs.
• The integration test-suite is successful, including:
  • pre-commit.ci tests pass.
  • tests pass for all relevant OS configurations (linux, osx, windows).
• Module documentation is up-to-date, including:
  • INTERFACE.yaml mentions all relevant pathvars and wildcards.
  • README.md describes how to use the module and has the necessary citations.

[irm-codebase]

@ddahawkins-TUDelft feel free to test this branch of the module. Should fix all your problems.
Keep in mind that this uses a new approach in the configuration (multi-scenario configurations are now supported).

[irm-codebase]

Rechecked all files.

• Tests pass.
• Dummy file lands on the top of resources/automatic/
• pathvars are used throughout the new rules.