Auto-heal corrupted Gemfile.lock with no specs

[duckinator]

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

If a Gemfile.lock has a mismatch between specs: and DEPENDENCIES, printing funding information runs what boils down to nil.metadata. This caused a NoMethodError to be raised.

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

If the lockfile is malformed, it should be regenerated.

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

[duckinator]

It turns out the failing test is the one that #6400 changes. And with those changes merged first, it works fine.

So I think the solution is merging #6400 first, and I revise this based to be based on that PR.

[duckinator]

I rebased off #6400, which is in the merge queue already. Once that's merged, I'll rebase off master again.

[deivid-rodriguez]

Is it ready for a review now @duckinator? It looks good to me!

[duckinator]

Yeah, this is good to go. Just forgot to switch it from draft to normal PR. I'm not at a computer atm, so you can go ahead and do that then merge it.

…

On Wed, Mar 1, 2023, at 9:04 AM, David Rodríguez wrote: Is it ready for a review now @duckinator <https://github.com/duckinator>? It looks good to me! — Reply to this email directly, view it on GitHub <#6423 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAJWESY6ICHAST5UQJ5YDDWZ5JOLANCNFSM6AAAAAAVLMRA4Q>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[deivid-rodriguez]

Done! Thanks for this @duckinator!