Updating Gemfile.lock for rubocop-rspec dependecy.

What does this MR do?

GDK pipeline is failing with this error:

Downloading rubocop-rspec-1.15.1 revealed dependencies not in the API or the
lockfile (rubocop (>= 0.42.0)).
Either installing with `--full-index` or running `bundle update rubocop-rspec`
should fix the problem.

Updated Gemfile.lock by running bundle update rubocop-rspec.

Are there points in the code the reviewer needs to double check?

No

Why was this MR needed?

gdk init in GDK pipeline failing, example https://gitlab.com/gitlab-org/gitlab-development-kit/-/jobs/28760758

Screenshots (if relevant)

N/A

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated
• API support added
• Tests
  • Added for this feature/bug
  • All builds are passing
• Review
  • Has been reviewed by UX
  • Has been reviewed by Frontend
  • Has been reviewed by Backend
  • Has been reviewed by Database
• Conform by the merge request performance guides
• Conform by the style guides
• Branch has no merge conflicts with master (if it does - rebase it please)
• Squashed related commits together

What are the relevant issue numbers?

N/A