Update dependencies and correct rubocop failure

[hsbt]

What was the end-user or developer problem that led to this PR?

In Ruby 3.3/3.4, bin/rubocop show the following warning.

$ bin/rubocop -A
/Users/hsbt/.local/share/gem/gems/rubocop-1.52.1/lib/rubocop/formatter/html_formatter.rb:3: warning: base64 was loaded from the standard library, but is not part of the default gems since Ruby 3.4.0. Add base64 to your Gemfile or gemspec. Also contact author of rubocop-1.52.1 to add base64 into its gemspec.

It fixed at recent released version of rubocop.

What is your fix for the problem, implemented in this PR?

I updated tool/bundler/*.lock and run bin/rubocop -A each cop rule.

Make sure the following tasks are checked

• Describe the problem / feature
• Write tests for features and bug fixes
• Write code to solve the problem
• Make sure you follow the current code style and write meaningful commit messages without tags

[koic]

This is a false positive in RuboCop. I've opened PR rubocop/rubocop#12607, but until that is resolved, it'll need to prevent false detections by using # rubocop:disable Style/RedundantParentheses.

[hsbt]

Thanks for your input!

[deivid-rodriguez]

@hsbt As per #7371 (comment), we may want to start using bin/rubocop -a when autocorrect and limit autocorrection to safe cops? To be honest, I always thought (until now) that -A was the "safe autocorrect" flag and -a was the unsafe one.

[koic]

This is a piece of trivia and can be remembered in the same way as git branch -d and git branch -D :-)
rubocop/rubocop#8156 (comment)

[deivid-rodriguez]

Makes sense, I guess the meaning was changed in v1, and that's why I thought -a corrected everything?

[koic]

I see. The concept of safety was not present initially, and there was only -a, which indeed is what -A is now 😅

[hsbt]

oh, I didn't know difference of -a and -A. Thanks.

I will use -a instead of -A in further works.