Make rust analyzer aspect follow rust_test.crate attribute

[hlopko]

Before, generated rust-project.json did not contain dependencies from the rust_library when rust_test used .crate attribute and the test was the only root in the targets attribute of rust_analyzer rule.

This PR depends on #754 and #760.

[hlopko]

CC @djmarcin

[UebelAndre]

Sorta feels like there's two changes here? They seem good but curious as to what brought on the harness attribute.

Oops, there's another PR 😅

But yeah, was it necessary for this or just a nicety?

[hlopko]

Sorta feels like there's two changes here? They seem good but curious as to what brought on the harness attribute.

Oops, there's another PR 😅

But yeah, was it necessary for this or just a nicety?

I pass a path to rust-project.json as a command line arg to the test.

• libtest doesn't support custom arguments
• It felt weird to have std::env::args() in a regular #[test].
• The code was a tiny little bit longer using libtest.

Now that I'm forced to think about this more, I found alternatives:

• pass the path to the rust-project.json through environment variable.
• access the file through runfiles.

I'm inclined to pursue the runfiles alternative (but I think the harness PR still makes sense and can go in).

[google-cla]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[hlopko]

@googlebot I fixed it.

[google-cla]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[google-cla]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[hlopko]

And finally we have a green CI. PTAL :)

[UebelAndre]

This looks good to me! a small nit and one question that's more of an aside 😅

[UebelAndre]

This looks good to me! Feel free to merge whenever you'd like 😄 and thanks!