Resolve "Running git clone with a secondary geo node URL has LFS batch download redirected to primary"

What does this MR do?

This MR fixes a regression introduced in 11.2 where cloning a repo/pulling down changes via HTTP, LFS updates would erroneously be pulled from the primary. As cloning/pulling down changes are read-only operations, they should be handled by the secondary.

What are the relevant issue numbers?

https://gitlab.com/gitlab-org/gitlab-ee/issues/7419

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• [ ] Documentation created/updated
• Tests added for this feature/bug
• Conforms to the code review guidelines
• Conforms to the merge request performance guidelines
• Conforms to the style guides
• [ ] Conforms to the database guides
• EE specific content should be in the top level /ee folder
• [ ] For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan?

Closes #7419 (closed)