Save original dependency requirement string in the database when publishing

[Turbo87]

This PR should resolve #3047 by saving the original dependency requirement string in the database when publishing, and returning the original string too when calling the GET /crates/:crate_id/:version/dependencies endpoint.

Before #2990 we were turning 1.2.3 into ^1.2.3 automatically. After that PR were turning it into >=1.2.3, <2.0.0, and now, with this PR, we would keep it at 1.2.3 and it would be up to the API client to prefix the ^, if necessary.

r? @jtgeibel

/cc @dtolnay

[bors]

☔ The latest upstream changes (presumably #3051) made this pull request unmergeable. Please resolve the merge conflicts.

Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:

@rustbot modify labels: +S-waiting-on-review -S-waiting-on-author

[bors]

☔ The latest upstream changes (presumably #3062) made this pull request unmergeable. Please resolve the merge conflicts.

Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:

@rustbot modify labels: +S-waiting-on-review -S-waiting-on-author

[bors]

☔ The latest upstream changes (presumably #3066) made this pull request unmergeable. Please resolve the merge conflicts.

Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:

@rustbot modify labels: +S-waiting-on-review -S-waiting-on-author

[jtgeibel]

@bors r+

[bors]

📌 Commit 815a218 has been approved by jtgeibel

[bors]

🔒 Merge conflict

This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again.

How do I rebase?

Assuming self is your fork and upstream is this repository, you can resolve the conflict following these steps:

1. git checkout semver-req (switch to your branch)
2. git fetch upstream master (retrieve the latest master)
3. git rebase upstream/master -p (rebase on top of it)
4. Follow the on-screen instruction to resolve conflicts (check git status if you got lost).
5. git push self semver-req --force-with-lease (update this PR)

You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial.

Please avoid the "Resolve conflicts" button on GitHub. It uses git merge instead of git rebase which makes the PR commit history more difficult to read.

Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Cargo.lock conflict is handled during merge and rebase. This is normal, and you should still perform step 5 to update this PR.

Error message

Auto-merging src/tests/krate/publish.rs
Auto-merging src/models/dependency.rs
CONFLICT (content): Merge conflict in src/models/dependency.rs
Automatic merge failed; fix conflicts and then commit the result.

[Turbo87]

@bors r=jtgeibel

[bors]

📌 Commit c50c536 has been approved by jtgeibel

[bors]

⌛ Testing commit c50c536 with merge 75563da...

[bors]

☀️ Test successful - checks-actions
Approved by: jtgeibel
Pushing 75563da to master...