Remove combined read only git messaging on free user efficiency

What does this MR do and why?

Related to #413013 (closed)

We don't have any plans to use the combined storage over limit and free user cap over limit CLI/git messaging anymore. So we are removing the functionality and the usage of it in lfs_request.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.