refactor: use the yml extension for every yaml file

The repository mixed both extensions, the molecule scenario used yml while the role itself used yaml. The yml
extension is the one ansible-galaxy and molecule generate and the one the sibling roles use, so it is applied
throughout.

The first_found lookups in tasks/main.yml name the candidate files explicitly and were adjusted accordingly, otherwise
the role would no longer find its distribution variables and its verification tasks.

Co-authored-by: Copilot <copilot@github.com>

tasks/main.yml

@@ -5,11 +5,11 @@
   vars:
     params:
       files:
-      - "{{ ansible_facts['distribution'] }}_{{ ansible_facts['architecture'] }}.yaml"
-      - "{{ ansible_facts['distribution'] }}.yaml"
-      - "{{ ansible_facts['os_family'] }}_{{ ansible_facts['architecture'] }}.yaml"
-      - "{{ ansible_facts['os_family'] }}.yaml"
-      - main.yaml
+      - "{{ ansible_facts['distribution'] }}_{{ ansible_facts['architecture'] }}.yml"
+      - "{{ ansible_facts['distribution'] }}.yml"
+      - "{{ ansible_facts['os_family'] }}_{{ ansible_facts['architecture'] }}.yml"
+      - "{{ ansible_facts['os_family'] }}.yml"
+      - main.yml
       paths:
       - vars
 
@@ -18,9 +18,9 @@
   vars:
     params:
       files:
-      - "{{ ansible_facts['distribution'] }}_verify_vars.yaml"
-      - "{{ ansible_facts['os_family'] }}_verify_vars.yaml"
-      - verify_vars.yaml
+      - "{{ ansible_facts['distribution'] }}_verify_vars.yml"
+      - "{{ ansible_facts['os_family'] }}_verify_vars.yml"
+      - verify_vars.yml
       paths:
       - tasks