Add method to base class to statically load results of
"semodule --list" command. Store output parsed into hash with keys
being module name and value being module version. Add prefetch method
to initially populate hash.

This change results in a substantial performance increase when checking
current resource state, on the order of 50% or more.

(MODULES-7319) Call "semodule --list" only once.

This commit updates the configuration file to point to the official Puppet VS Code Extension `puppet.puppet-vscode`

(maint) Update Puppet VS Code Extension ID

Added GitHub Actions workflows for `Static Code Analysis` and `Unit
Tests` that run each time there is a new `pull request` or `git push`.
`Unit tests` are also set to run every workday at `05:00:00 UTC`.

The `.yaml` config file for `Travis` has been removed.

In preparation for the Puppet 7 release, the
`puppet-module-posix-dev-r2.7` and `puppet-module-posix-dev-r2.7` gems
had to be removed from `Gemfile` due to the following dependency error:
  `puppet-module-posix-dev-r2.7` depends on
    `puppet_litmus` which depends on
      `bolt` which depends on
        `puppet` which is locked to a version below 7

Also added the needed gems that were lost in the above removal process.

This commit adds the `commits` rake task which is run in the Static Code
Analysis workflow as a step.

(MODULES-10849) Add GitHub Actions workflows

Due to unknown environment changes in GitHub Actions runners, we
encountered the following error:
`fatal: cannot create directory: Filename too long`

This commit allows git to use long paths in our GitHub Actions
workflows.

…paths-in-gh-actions

(maint) Allow git to use long paths in GitHub Actions

Create a separate group in the Gemfile for pdk and puppet-blacksmith
which are only used for releasing. In the workflow, avoid installing the
release group.

Update the workflow that tests with released Puppet gems to also test
with Puppet 7.

Remove testing with Puppet 5 from the workflows since it reached EOL.

Bump Ruby version in the static code analysis workflow to 2.6, as 2.5
will be EOL soon.

(MODULES-10945) Core module spring cleaning 2021

To avoid having to update this everytime we release a new agent
platform, it should be enough to specify the supported OS, without
specific versions. It is assumed that for each OS in metadata.json, the
versions supported are the same as what the agent itself supports.

(MODULES-10980) Release prep for 1.1.0