Fix incorrect documentation URLs when using `rubocop --show-docs-url`

Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>

Drop Ruby 2.5 runtime support

Follow rubocop/rubocop#10577.

This PR drops Ruby 2.5 runtime support and fixes the following build error.
https://github.com/utkarsh2102/rubocop-packaging/runs/7688082957

Fix compatibility with Rubocop 1.33.0

This commit suppresses the following RuboCop offenses.

```console
% bundle exec rubocop
(snip)

spec/rubocop/cop/packaging/bundler_setup_in_tests_spec.rb:18:25: C:
[Correctable] Style/EmptyHeredoc: Use an empty string literal instead of
heredoc.
      expect_correction(<<~RUBY)
                        ^^^^^^^
spec/rubocop/cop/packaging/bundler_setup_in_tests_spec.rb:33:25: C:
[Correctable] Style/EmptyHeredoc: Use an empty string literal instead of
heredoc.
      expect_correction(<<~RUBY)
                        ^^^^^^^
spec/rubocop/cop/packaging/gemspec_git_spec.rb:82:24: C: [Correctable]
Style/EmptyHeredoc: Use an empty string literal instead of heredoc.
    expect_no_offenses(<<~RUBY)
                       ^^^^^^^

21 files inspected, 3 offenses detected, 3 offenses autocorrectable
```

…ub_actions

Migrate CI to GitHub Actions

Remove `spec.test_files` from `Packaging/GemspecGit`'s doc

Follow up to rubocop/rubocop#10065 (comment).

This PR removes `spec.test_files` from `Packaging/GemspecGit`'s doc.

Drop Ruby 2.4 support

Follow up to 6972a97
and rubocop/rubocop#9648.

I am so excited, letz see how it goes! ^.^

Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>

Yeah, the extra "tip" is somewhat annoying at
the moment. Maybe take a raincheck on this!?

Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>

Fixes the warning: obsolete parameter ExcludedMethods
(for Metrics/BlockLength) found in .rubocop.yml
`ExcludedMethods` has been renamed to `IgnoredMethods`.

Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>

Fix compatibility spelling

s/compatibility/compatibility/g

Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>

Since all the cops are enabled by default, it
doesn't make sense to explicitly set the
"Enabled" field to "true". It's obvious that it is.

Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>

Also allow it to fail since it's a wild
playground of new features.

Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>

Now that ruby2.7.2 is out, let's use that
rather than ruby2.7.1.

Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>

Loosen requirement of RuboCop

…ng_adoc

Fix HTML id attribute in cops_packaging.adoc

This PR fixes the following HTML id attribute in cops_packaging.adoc.

```console
% git grep require-relative-hardcoding-lib-rationale
docs/modules/ROOT/pages/cops_packaging.adoc:=== Rationale
[[require-relative-hardcoding-lib-rationale]]
docs/modules/ROOT/pages/cops_packaging.adoc:=== Examples
[[require-relative-hardcoding-lib-rationale]]
```

It will suppress the following warning that generates docs.rubocop.org.

```console
$ cd docs.rubocop.org
$ antora --pull antora-playbook.yml
(snip)

asciidoctor: WARNING: cops_packaging.adoc: line 205: id assigned to
section already in use: require-relative-hardcoding-lib-rationale
```

This is based on the comment and the discussion
of #rubocop/rubocop/issues/8748#issuecomment-699478216

Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>

Unfortunately, I missed this line while fixing
the description of the cops. Sigh.

Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>

Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>

Since the tests are mocked, disable Lint/InterpolationCheck
because their autocorrect breaks the tests (since they're
mocked :)).

Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>

Add tests to check if the interpolated require calls
are correctly being caught by the RequireHardcodingLib
cop and that the autocorrect for it is working fine
as well.

Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>

Style/StringConcatenation's autocorrect hinders with the
existing AST pattern of RequireHardcodingLib to catch
offensive require calls.

So add the interpolated AST to catch those lines as well.

Fixes: #30

Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>

Make it a bit more clearer as to what's
problematic and what to do intead of those
lines of code.

Signed-off-by: Utkarsh Gupta <utkarsh@debian.org>