feat: update all platforms for PostgreSQL 13 (inc. `use_upstream_repo` in CI)

[myii]

PR progress checklist (to be filled in by reviewers)

• [ ] Changes to documentation are appropriate (or tick if not required)
• [ ] Changes to tests are appropriate (or tick if not required)
• [ ] Reviews completed

---

What type of PR is this?

Primary type

• [ ] [build] Changes related to the build system
• [ ] [chore] Changes to the build process or auxiliary tools and libraries such as documentation generation
• [x] [ci] Changes to the continuous integration configuration
• [x] [feat] A new feature
• [x] [fix] A bug fix
• [ ] [perf] A code change that improves performance
• [ ] [refactor] A code change that neither fixes a bug nor adds a feature
• [ ] [revert] A change used to revert a previous commit
• [ ] [style] Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)

Secondary type

• [ ] [docs] Documentation changes
• [x] [test] Adding missing or correcting existing tests

Does this PR introduce a BREAKING CHANGE?

No.

Related issues and/or pull requests

Follow-up for #314, based on this https://github.com/saltstack-formulas/postgres-formula/pull/314#issuecomment-874674266.

Describe the changes you're proposing

Allow PostgreSQL 13 to be installed on all supported platforms.

Update the CI to reflect that by using use_upstream_repo for all possible platforms.

Pillar / config required to test the proposed changes

As provided.

Debug log showing how the proposed changes work

As shown in GitLab CI (Linux) and GitHub Actions (FreeBSD).

Documentation checklist

• [ ] Updated the README (e.g. Available states).
• [ ] Updated pillar.example.

Testing checklist

• [x] Included in Kitchen (i.e. under state_top).
• [x] Covered by new/existing tests (e.g. InSpec, Serverspec, etc.).
• [x] Updated the relevant test pillar.

Additional context

[myii]

Updated the method here to use two separate tests suites instead of trying to do everything from just the one. Also taking advantage of the share suite to put common controls there.

The benefit to this method is that the formula is being tested fully for both installing from the upstream repo or not. The instances where both methods are available run both suites in the same job.

Part of these changes were automated using https://github.com/myii/ssf-formula/pull/348.

[saltstack-formulas-travis]

:tada: This PR is included in version 0.43.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: