Fix double colons in questions asked from GemcutterUtilities

[technicalpickles]

At some point, this is using Thor, and it automaticlaly adds a trailing : with space, so we don't need to do it ourselves.

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

I was using https://github.com/rubygems/configure_trusted_publisher and got minorly annoyed by the double : prompts:

Enter your RubyGems.org credentials.
Don't have an account yet? Create one at https://rubygems.org/sign_up

Username/email: : pickles@example.com

      Password: : 
You have enabled multi-factor authentication. Please enter OTP code.

Code: : 12345678

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

Update these ask calls to not include the :

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

[technicalpickles]

The tests are failing because there isn't a colon 😅 I wonder if it has to do with the thor version?

[deivid-rodriguez]

I don't think RubyGems uses thor. Bundler uses thor, but uses a fixed version so even then thor version should be irrelevant. So maybe it's something else? I'm unsure about what could cause this.

[technicalpickles]

Well, I can reproduce the test failure locally at least.

The place I observed it was in https://github.com/rubygems/configure_trusted_publisher ... my output is identical to the readme, ie:

$ gem exec configure_trusted_publisher rubygem
Configuring trusted publisher for rubygem0 in /Users/segiddins/Development/github.com/rubygems/configure_trusted_publisher for rubygems/configure_trusted_publisher

Enter your https://rubygems.org credentials.
Don't have an account yet? Create one at https://rubygems.org/sign_up
Username/email: : gem-author
      Password: :

  1) Automatically when a new tag matching v* is pushed
  2) Manually by running a GitHub Action

How would you like releases for rubygem0 to be triggered? (1, 2) [2]: 2

Successfully configured trusted publisher for rubygem0:
  https://rubygems.org/gems/rubygem0/trusted_publishers

Specifically, Username/email and Password have extra : in them.