At that time, people were not abusing Gitlabs services by crypto mining on their shared runners. The credit card verification was added for new users. That means, that from the day that was activated, new users were required to verify. For everyone who was registered and using shared runners prior to that date, didn’t have to verify. The feature hasn’t been taken away, you can still use the shared runners, but are required to verify because of the people that were abusing the service. If you want to blame anyone for that, blame the people who were abusing Gitlab’s services. Had nobody abused it, then no-one would have been asked to verify, and it would have been the same as it was previously available without verification.
You are confusing the situation since nothing has been removed, no feature has been taken away. If shared runners had been removed entirely, and that nobody could use them - that is taking something away. They are still there for use, you just need to verify first - it stops people abusing Gitlab’s resources. It’s purely an additional step to verify valid users who will not attempt to abuse Gitlab’s services.
You can disable shared runners on your project and create your own runners, then nobody needs to verify, and you can do everything you want on your own, private runners.
I don’t use runners, I have my own Gitlab installation on my premises, and I adminster this. I have no need for runners, but all the information was communicated via Gitlab about the abusers on the forum and what was required to continue using their shared runner service via gitlab.com.