(PE-36462) Rubocop updates (#379)

Updated Rubocop config.
Generated TODO and fixed minor issue.

Author: ragingra

.rubocop.yml

@@ -3,8 +3,11 @@ require:
 - rubocop-performance
 - rubocop-rspec
 AllCops:
+  Newcops: enable
+  ExtraDetails: true
+  DisplayStyleGuide: true
   DisplayCopNames: true
-  TargetRubyVersion: '2.6'
+  TargetRubyVersion: '2.7'
   Include:
   - "**/*.rb"
   Exclude:

.rubocop_todo.yml

@@ -0,0 +1,7 @@
+# This configuration was generated by
+# `rubocop --auto-gen-config`
+# on 2023-09-05 10:29:15 UTC using RuboCop version 1.48.1.
+# The point is for the user to remove these configuration records
+# one by one as the offenses are removed from the code base.
+# Note that changes in the inspected code, or installation of new
+# versions of RuboCop, may require this file to be generated again.

spec/functions/fail_on_transport_spec.rb

@@ -25,7 +25,7 @@
   # Function testing depends on rspec-puppet magic in the opening describe
   # statement. Re-defining the subject just to give it a different name
   # would require duplicating rspec-puppet code, and that's a far worse sin.
-  # rubocop:disable Rspec/NamedSubject
+  # rubocop:disable RSpec/NamedSubject
   it 'raises an error when nodes use the specified transport' do
     expect { subject.execute(nodes, 'pcp') }.to raise_error(Puppet::PreformattedError, %r{target\.example uses pcp transport: This is not supported\.})
   end
@@ -37,5 +37,5 @@
   it 'raises no error when nodes do not use the specified transport' do
     expect { subject.execute(nodes, 'ssh') }.not_to raise_error
   end
-  # rubocop:enable Rspec/NamedSubject
+  # rubocop:enable RSpec/NamedSubject
 end