chore: pin ansible-lint to 6.13.1

ansible-lint was updated and the GitHub
action did not pin the dependency, resulting
in the repository to fail sanity tests.

Updating the repository to adhere to new fatal
linter rules, but also pinning the linter to
prevent failures that may be unrelated to the
particular commit.

Updating usages for python3.8 to 3.9 as ansible-lint
is dropping support for 3.8.

.github/workflows/ansible-test.yml

@@ -36,7 +36,7 @@ jobs:
         # validate-modules cannot be turned on until #498 is resolved.
         run: ansible-test sanity -v --color --skip validate-modules
       - name: Install ansible-lint
-        run: pip install ansible-lint
+        run: pip install ansible-lint==6.13.1
       - name: Run ansible-lint
         run: ansible-lint
   unit:

.github/workflows/gcloud.yml

@@ -30,10 +30,10 @@ jobs:
         with:
           path: ansible_collections/google/cloud
 
-      - name: Set up Python 3.8
+      - name: Set up Python 3.9
         uses: actions/setup-python@v1
         with:
-          python-version: 3.8
+          python-version: 3.9
 
       - name: Install dependencies
         run: |

.github/workflows/gcsfuse.yml

@@ -25,10 +25,10 @@ jobs:
         with:
           path: ansible_collections/google/cloud
 
-      - name: Set up Python 3.8
+      - name: Set up Python 3.9
         uses: actions/setup-python@v1
         with:
-          python-version: 3.8
+          python-version: 3.9
 
       - name: Install dependencies
         run: |