CI rspec job consistently fails with payment method related errors

### Problem

Our Ci pipelines rspec job consistently started to fail on `2022-04-01` with payment method related errors. This prevents us from merging merge requests or sending merge requests into review.

Errors from a pipeline:

<details>

```
1) purchase new cloud subscriptions without payment methods successfully purchase a GitLab.com subscription
     Failure/Error: objects = IronBank::Actions::Create.call(type: 'PaymentMethod', objects: [instance.remote])
     IronBank::BadRequestError:
       Body: [{"Success"=>false, "Errors"=>[{"Code"=>"INVALID_VALUE", "Message"=>"Expiration date must be a future date."}]}]
     # ./spec/factories/z/payment_methods.rb:20:in `block (3 levels) in <top (required)>'
     # ./spec/factories/z/accounts.rb:27:in `block (4 levels) in <top (required)>'
     # ./spec/factories/customers.rb:23:in `block (4 levels) in <top (required)>'
     # ./spec/features/new_gitlab_subscription_spec.rb:22:in `block (2 levels) in <top (required)>'
     # ./spec/features/new_gitlab_subscription_spec.rb:26:in `block (2 levels) in <top (required)>'
  2) Payment Methods with payment methods removes the payment method
     Failure/Error: objects = IronBank::Actions::Create.call(type: 'PaymentMethod', objects: [instance.remote])
     IronBank::BadRequestError:
       Body: [{"Success"=>false, "Errors"=>[{"Code"=>"INVALID_VALUE", "Message"=>"Expiration date must be a future date."}]}]
     # ./spec/factories/z/payment_methods.rb:20:in `block (3 levels) in <top (required)>'
     # ./spec/factories/z/accounts.rb:27:in `block (4 levels) in <top (required)>'
     # ./spec/factories/customers.rb:23:in `block (4 levels) in <top (required)>'
     # ./spec/features/payment_methods_spec.rb:89:in `block (3 levels) in <top (required)>'
     # ./spec/features/payment_methods_spec.rb:36:in `block (2 levels) in <top (required)>'
  3) purchase new EE Subscriptions when payment method does not exist successfully purchase an EE subscription
     Failure/Error: objects = IronBank::Actions::Create.call(type: 'PaymentMethod', objects: [instance.remote])
     IronBank::BadRequestError:
       Body: [{"Errors"=>[{"Message"=>"Expiration date must be a future date.", "Code"=>"INVALID_VALUE"}], "Success"=>false}]
     # ./spec/factories/z/payment_methods.rb:20:in `block (3 levels) in <top (required)>'
     # ./spec/factories/z/accounts.rb:27:in `block (4 levels) in <top (required)>'
     # ./spec/factories/customers.rb:23:in `block (4 levels) in <top (required)>'
     # ./spec/features/new_ee_subscription_spec.rb:6:in `block (2 levels) in <top (required)>'
     # ./spec/features/new_ee_subscription_spec.rb:11:in `block (2 levels) in <top (required)>'

6324 examples, 3 failures, 1 pending
Failed examples:
rspec ./spec/features/new_gitlab_subscription_spec.rb:57 # purchase new cloud subscriptions without payment methods successfully purchase a GitLab.com subscription
rspec ./spec/features/payment_methods_spec.rb:99 # Payment Methods with payment methods removes the payment method
rspec ./spec/features/new_ee_subscription_spec.rb:39 # purchase new EE Subscriptions when payment method does not exist successfully purchase an EE subscription
```

</details>

**Note:** This issue was created afterwards. Investigation happened in this [Slack thread](https://gitlab.slack.com/archives/C029YFPUA6M/p1648805872934929).

### Proposal

Investigate the root cause and work on a fix.

### Result

Fixed CI pipelines and unblock merge request merges and merge requests in general.

### Next steps (if any)

Investigate the failure.

### How will we measure success?

Green pipeline results for the `rspec` job

Story points: 3.0