Release v0.17.0

* Remove version constraints for rubocop, rubocop-performance, and rubocop-rails
* Test against Ruby 3.1

Bump all dev dependencies

This commit bumps all development dependencies, and removes pessimistic
version constraints where possible now that we've got a Gemfile.lock checked
in.

We had to keep the constraint for Rails for now, since Rails 7 is not
compatible with Ruby 2.6. We can bump Rails if we drop Ruby 2.6.

None of this affects the released gem, so as long as tests still pass we
are in good shape.

Test against Ruby 3.1

Remove version constraints for rubocop libraries

Related to removing version constraints in 286944a,

Running locked version of these in CI will help avoid unexpected
failures for unrelated changes.

These constraints make it more difficult to upgrade these libraries in
projects that use rubocop-github.

I think the idea here was that we'd be able to bump the version
alongside the default config, but without locking to an exact version we
can still end up with a config that is incompatible with certain rubocop
version (see the unrecognized cop error in
#86, for example).

If anything, I'd prefer a `>=` constraint over a `<=`. That would allow
us to bump the minimum constraint when we add new cops, but still
freely upgrade in our projects as long as there are no config
incompatibilities (which are less common anyway ever since RuboCop 1.0).

STYLEGUIDE.md: consistent ordering of bad and good

STYLEGUIDE.md: consistent use of parenthesis on Keyword Arguments

release v0.16.2

Add support for rendering ViewComponents `with_content`

https://github.com/rubocop/rubocop-ast/blob/master/docs/modules/ROOT/pages/node_pattern.adoc
^ Was JUST enough context for me to figure this out!

…_content

Bump rubocop & rubocop-performance version

Version 1.4 of rubocop introduced a breaking change that creates some
warnings and issues when using `parser/ruby27`, this issue was fixed in
rubocop/rubocop#9702 and released in 1.13.0

Enforce local keys being literals

Add check for insecure hash algorithms

Update gems for ruby 3

update minitest from 5.10 to 5.14
update rubocop to 1.6.1

https://api.rubyonrails.org/classes/Digest/UUID.html

uuid_v3 uses MD5, so it's only allowed when MD5 is in the "Allowed"
list. uuid_v5 uses SHA1, so it's only allowed when SHA1 is in the
"Allowed" list.