CI: Avoid GH throttling via Consolidation

#### Issue:
Our CI can fail due to GitHub throwing a 429.
i.e: Too many CI actions tried to pull from the repo and GitHub throttled us.

There are two causes of this:
1. We use GH Workflow Matrices, which spawn a job per entry
2. Every Dependabot PR updates on a merge

Thus the requests to pull the Repo from GitHub is:
```
|dependabot_prs| x 79
```
Where 79 is the current number of individual GitHub actions created through our matrix use.

#### A Solution:
Too prevent this in the future, we should consolidate are GitHub Workflow Jobs.

Technically, a Job could run all the tox envs for a OS Version,
even across Python versions.

That would dramatically reduce the requests to pull the repo down.

This reduce the number GitHub Jobs and increase the Steps per Job.

We would loose some of our high level test reporting,
but I believe that is acceptable.

_Originally posted by @texastony in https://github.com/aws/aws-encryption-sdk-python/issues/564#issuecomment-1441033254_

Inizia individuando le definizioni della matrice di GitHub Workflow e verificando come gli ambienti tox sono distribuiti tra i job per sistema operativo e versione di Python. Confronta il numero attuale di job con una disposizione consolidata, quindi verifica che CI continui a eseguire tutti gli ambienti tox e a segnalare gli errori in modo accettabile senza attivare il throttling di GitHub.

Scritto dal modello di indicizzazione a partire dal testo della issue.