Multiple areas of ligare-scaffold do not render Database-module relevant templates depending on CLI argument order

[aholmes]

The issue #149 describes a failure of the scaffolder Test module to render Database-module relevant information depending on the order in which modules are specified at the command line. It turns out the Test module is not the only affected code. Because PR #151 exists, and I don't want to inflate the scope of the fix, this issue tracks the same problem for other locations in code.

src/web/Ligare/web/scaffolding/templates/base/docs/CONFIGURATION.md.j2
9:{% if module.database %}

src/web/Ligare/web/scaffolding/templates/base/{{application.module_name}}/__init__.py.j2
6:{% if module.database %}
37:    {% if module.database %}

src/web/Ligare/web/scaffolding/templates/basic/{{application.module_name}}/config.toml.j2
3:connection_string = '{{module.database.connection_string}}'

src/web/Ligare/web/scaffolding/templates/optional/{{application.module_name}}/endpoints/{{operation.module_name}}.py.j2
5:{% if module.database %}
10:{% if module.database %}
23:{% if module.database %}
32:{% if module.database %}

src/web/Ligare/web/scaffolding/templates/optional/{{application.module_name}}/modules/test/templates/test_{{meta.operation.module_name}}.py.j2
9:{% if module.database %}
27:{% if module.database %}

src/web/Ligare/web/scaffolding/templates/openapi/{{application.module_name}}/openapi.yaml.j2
25:      {% if module.database %}
39:    {% if module.database %}

src/web/Ligare/web/scaffolding/templates/openapi/{{application.module_name}}/config.toml.j2
3:connection_string = '{{module.database.connection_string}}'