RuboCop now uses prism as a first-class (translation) parser

Since rubocop 1.75 it just does the right thing, so no need to mention much of the old
configuration anymore.

Author: Earlopain

docs/parser_translation.md

@@ -25,24 +25,6 @@ If you also need to parse Ruby versions below 3.3 (which `prism` has no support
 
 ### RuboCop
 
-Prism as a parser engine is directly supported since RuboCop 1.62.
+Prism as a parser engine is directly supported since RuboCop 1.75. Simply specify a `TargetRubyVersion` >= 3.4 and the `prism` parser translation will be used to analyze your code.
 
-First, specify `prism` in your Gemfile:
-
-```ruby
-gem "prism"
-```
-
-To use Prism with RuboCop, specify `ParserEngine` and `TargetRubyVersion` in your RuboCop configuration file:
-
-```yaml
-AllCops:
-  ParserEngine: parser_prism
-  TargetRubyVersion: 3.3
-```
-
-The default value for `ParserEngine` is `parser_whitequark`, which indicates the Parser gem. You need to explicitly switch it to `parser_prism` to indicate Prism. Additionally, the value for `TargetRubyVersion` must be specified as `3.3` or higher, as Prism supports parsing versions of Ruby 3.3 and higher.
-The parser class is determined by the combination of values for `ParserEngine` and `TargetRubyVersion`. For example, if `TargetRubyVersion: 3.3`, parsing is performed by `Prism::Translation::Parser33`, and for `TargetRubyVersion 3.4`, parsing is performed by `Prism::Translation::Parser34`.
-
-For further information, please refer to the RuboCop documentation:
-https://docs.rubocop.org/rubocop/configuration.html#setting-the-parser-engine
+Initial support was added in RuboCop 1.62, with an explicit opt-in to use `prism` via the `ParserEngine` configuration. This is no longer necessary.