[match] Check validity of provisioning profile certificates when force_for_new_certificates option is provided

[nekrich]

Checklist

• I've run bundle exec rspec from the root directory to see all new and existing tests pass
• I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
• I've read the Contribution Guidelines
• I've updated the documentation if necessary.

Motivation and Context

When a certificate expires (not revoked) provisioning profile stays valid.
And if we regenerate certificate count will not differ:

• For portal certificates, we filter out the expired one but includes a new certificate;
• Profile still contains an expired certificate and is valid.
  Thus, we need to check the validity of profile certificates too.

It's my bad that I wasn't counting that the provisioning profile stays valid when certificates expire.

Description

Simplty add .select(&:valid?) 😅

Testing Steps

• Get the certificate contained in the provisioning profile expired 🤷
• match(force_for_new_certificates: true)

[joshdholtz]

Ohhhhhh, this is a great catch! Thanks for fixing this 🙌

[fastlane-bot]

Congratulations! 🎉 This was released as part of fastlane 2.205.2 🚀