Followed up CVE-2022-39253 for bundler examples

	---
	 spec/bundler/cache/git_spec.rb           | 3 +++
	 spec/bundler/install/gemfile/git_spec.rb | 9 +++++++++
	 spec/bundler/update/git_spec.rb          | 3 +++
	 3 files changed, 15 insertions(+)

	Use valid tokens as cookie names

	---
	 spec/ruby/library/cgi/cookie/name_spec.rb  | 12 ++++++------
	 spec/ruby/library/cgi/cookie/parse_spec.rb | 10 +++++-----
	 2 files changed, 11 insertions(+), 11 deletions(-)

And not depend on the state of rack's master branch, in particular, on
their Ruby support range.

`RSpec::Mocks::ArgumentListMatcher#args_match?` fails when a
non-keywords hash is passed while a keyword hash is expected.

This is a change in `rspec-mocks` 3.10.3, so we need to adapt to it.

These failures are caused by the incompatibility in keyword argument
treatment in rspec-mocks.
I fix the expectations in the bundler/rubygems_integration_spec.rb.
These tests are not touched in the master branch.
It seems that the following patch also fix the failures.
But I believe the expectations in these tests are wrong. We should pass a Hash literal explicitly.

--- a/common.mk
+++ b/common.mk
@@ -1365,7 +1365,7 @@ yes-test-bundler-precheck: main
 no-test-bundler-prepare: no-test-bundler-precheck
 yes-test-bundler-prepare: yes-test-bundler-precheck
        $(XRUBY) -C "$(srcdir)" bin/gem install --no-document \
-               --install-dir .bundle --conservative "rspec:~> 3.8" "rake:~> 13.0" "parallel_tests:~> 2.29"
+               --install-dir .bundle --conservative "rspec-core:= 3.10.1" "rspec-expectations:= 3.10.1" "rspec-mocks:= 3.10.2" "rake:~> 13.0" "parallel_tests:~> 2.29"

 RSPECOPTS =
 BUNDLER_SPECS =

	[rubygems/rubygems] Fix spec to not touch the network

	And not depend on the state of rack's master branch, in particular, on
	their Ruby support range.

	https://github.com/rubygems/rubygems/commit/9ea4baffac
	---
	 spec/bundler/commands/remove_spec.rb | 4 +++-
	 1 file changed, 3 insertions(+), 1 deletion(-)