Enhancement/versioned config templates

[Salvoxia]

blocky frequently changes the structure of its config file, deprecating older config structures and eventually invalidating them.
The config template this role has used produces several deprecation warnings on startup for upstream, blackLists and whiteLists which are replaced by upstreams, denylists and allowlists.

This PR adds versioned config templates for blocky. The role can now contain several different config templates. A configuration defines a min_version and/or max_version for each config template. The role dynamically detects the correct template to use depending on the value of blocky__version.
It is up to the role's maintainer to update that configuration whenever a new blocky version with configuration changes is released.

# Must be maintained as blocky evolves. min_version and max_version may be defined for the same template.
blocky__config_template_versions: [
  {'max_version': '0.23', 'template': 'config.yaml.up_to_0.23.j2'},
  {'min_version': '0.24', 'template': 'config.yaml.from_0.24.j2'},
]

This approach is able to easily manage changes in configuration structure as long as these changes do not affect the structure of role variables. Changes to role variable structures can be implemented with more complex jinja2 templating in the config template.

Molecule tests for different blocky versions ranging from v0.21 to v0.24 have been introduced as part of the matrix.
Note: Tests for rockylinux9 have ben temporarily disabled due to this issue.

[resmo]

looks solid, thanks for this contribution.