feat(build): preserve repository name case for build upload

[runningcode]

Why make this change?
Github is not case sensitive to repository names but our database is sensitive. This means that if we look up a repository name with different casing, we won’t get a match on the database. We decided to make the change to the CLI because if there were ever a provider that did use case sensitive repository names then we would not be able to support it with the given database. See linked Linear issue for the discussion.

This PR adds a parameterized version of the parse function for use in the build upload feature so that we don’t affect other features that use the parse function.

Two alternate approaches are possible

1. remove the explicit lowercasing in the parse function but I wasn’t sure how that would affect other features.
2. implement a separate parse_preserve_case function without adding the extra parameter to the existing function but that approach would yield too much duplicate code.

Fixes EME-312

🤖 Generated with Claude Code

[linear]

EME-312 Repository name is case sensitive

[szokeasaurusrex]

Looks good in principle, but I think we can greatly simplify this implementation.

Rather than adding an extra preserve_case parameter to from_git_parts, let's preserve that function's original signature, but instead, always return the original strings from there; i.e., we would refactor from_git_parts to always preserve case.

Then, we can add a separate method on VcsUrl called to_lowercase, which would look like the following:

fn to_lowercase(mut self) {
    self.id = self.id.to_lowercase();
    self
}

And then, we modify the parse function to call

Self::parse_impl(url).to_lowercase()

I greatly would prefer this solution, as it will eliminate the repetitive if preserve_case blocks in from_git_parts

[runningcode]

I had these two clippy warning with function you suggested so I adjusted it to what I have in the code.

warning: methods with the following characteristics: (`to_*` and `self` type is not `Copy`) usually take `self` by reference
        --> src/utils/vcs.rs:136:21
         |
     136 |     fn to_lowercase(mut self) -> VcsUrl {
         |                     ^^^^^^^^
         |
         = help: consider choosing a less ambiguous name
         = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#wrong_self_convention
         = note: `#[warn(clippy::wrong_self_convention)]` on by default

  warning: methods with the following characteristics: (`to_*` and `self` type is not `Copy`) usually take `self` by reference
        --> src/utils/vcs.rs:136:21
         |
     136 |     fn to_lowercase(self) -> VcsUrl {
         |                     ^^^^
         |
         = help: consider choosing a less ambiguous name
         = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#wrong_self_convention
         = note: `#[warn(clippy::wrong_self_convention)]` on by default

[szokeasaurusrex]

Yeah, if clippy complained, then this is the right thing to do!

[runningcode]

Thanks @szokeasaurusrex that’s a good suggestion. I think I applied it as you suggested with one exception noted in my comment above. Let me know if there is a better alternative.