Adds a shared pipeline for gems verify workflow

[cgranleese-r7]

This PR adds two new shared pipelines for testing gems. One for testing gems with Rails and another for without. The idea here was to now have one centralized point of truth for testing our gems.

The shared pipeline will support inputs for dependencies and testing commands e.g.

  build:
    uses: cgranleese-r7/metasploit-framework/.github/workflows/shared_gem_verify.yml@add-gem-verify-shared-pipeline
    with:
      dependencies: '["graphviz"]'
      test_commands: |
        bundle exec rake spec
        bundle exec rake cucumber
        bundle exec rake yard

Initially the corresponding gem PRs will point at these new pipelines on my @cgranleese-r7 repository for testing. Once this is landed, I will rebase those PRs.

Gems PRs:

• Updates verify workflow to use shared pipeline metasploit-concern#45
• Updates verify workflow to use shared pipeline metasploit-credential#189
• Updates verify workflow to use shared pipeline metasploit-model#73
• Updates verify workflow to use shared pipeline metasploit_data_models#216
• Updates verify workflow to use shared pipeline rex-core#43
• Updates verify workflow to use shared pipeline rex-exploitation#46
• Updates verify workflow to use shared pipeline rex-mime#9
• Updates verify workflow to use shared pipeline rex-powershell#45
• Updates verify workflow to use shared pipeline rex-random_identifier#15
• Updates verify workflow to use shared pipeline rex-socket#73
• Updates verify workflow to use shared pipeline rex-sslscan#10
• Updates verify workflow to use shared pipeline rex-text#73

Verification

• Ensure code changes are sane
• Verify gem PRs are passing and being tested as expected

[jmartin-tech]

Just an opinion here, this seems to create a circular dependency in the github actions where sub-gems repos are now dependent on the state of a repo that consumes them. It might be better to create a repo that holds shared actions or to have the action defined in a repo that does not have dependencies.

[adfoster-r7]

@jmartin-tech Thanks! I also think having it in a centralized repo could also reduce the checkout time for faster CI runs by a bit, but we'll keep things simple as a first pass and can revisit it if there's any issues with future upgrade efforts 🤞