Fix badges

Trigger Github workflow for merges

A merge is viewed by Github as a push to the branch where the merge
occurs, see https://github.community/t/trigger-workflow-only-on-pull-request-merge/17359/2
This means we should have coverage reports for merge commits from
Github, which should result in saner numbers.

Fetch parent commits

CI platforms do not run their jobs on the commit you push. Instead, they
run it on a merge commit so that both your changes and the latest
version of the target branch are taken into account.
Before uploading the coverage report, CodeCov's bash uploader attempts
to find the original commit hash, and succeeds on Travis and AppVeyor,
but not on Github, because the method it uses does not work unless the
parent commits are fetched too, which results in Github posting to
CodeCov with a different hash than Travis or AppVeyor.
Setting the fetch depth fixes that issue.

Add GitHub Actions builds for oci8 and pdo_oci drivers

Clean up inconsistent or redundant argument names

Remove parameters and types unset after statement execution

Update doctrine/coding-standard to 8.1

Remove workaround in PDOSqlsrv\Connection::quote()

respect to platform restrictions when creating autoincrement identifier name

Rework extension detection in tests

Use relative names in inline {@link} annotations where possible