Update pipeline/Github actions

[jtroussard]

Seems the coverage report and tests are not kicking off. Would like to update/fix this as part of the 1.3.1 milestone.

[JonathanHuot]

I would consider this work as critical as it will help other PRs to be merged into master.

[jtroussard]

@JonathanHuot Looks like the coveralls and branch protection features are running. I know we had a bit of a discussion about the way the coverall coverages were being calculated but can we confirm where we wanted to cut a release? Do we want to wait for a more substantial test of the branch protection features/coveralls coverage check? Do we want to include the documentation reformat/update into this milestone?

[jtroussard]

@JonathanHuot Looks like 1.3.1 is wrapping up nicely. Are we ready to cut a release?

[JonathanHuot]

@jtroussard , yes let's cut the release!

[jtroussard]

@JonathanHuot I wanted to discuss this when you have a moment.

• Relevant line calculation difference between python versions, related to -0.0% change? lemurheavy/coveralls-public#1608 (comment)
• https://stackoverflow.com/questions/70570733/does-it-make-sense-to-run-code-coverage-against-different-language-versions

related to pipeline failing good(?) PRs

• Updates docs in oauth_session1 to match existing pattern #478 (comment)