feat: validate build target for AWS Lambda, and check target component in toolchain

[rnag]

Hi @calavera, just creating this as a draft PR for you to review when you have time; hopefully this resolves #30.

I've also added a test for adding the target component to the toolchain, and confirmed it works as expected. It looks like the check to confirm if a target component is present in the toolchain should be "zero cost", as it involves just a lookup to see if a directory exists or not in the rustup home.

--

Below are the changes added as part of this feature:

• validate that the build target passed in to --target is currently supported for deployments to AWS Lambda
• check if the target component is installed in the host toolchain, and install it with rustup target add <component> if needed

[calavera]

This looks really good @rnag !

[rnag]

Awesome, am glad to hear it! I went ahead and marked this PR as open for review in that case.

I also marked the one test as ignored since it's technically an integration test, and ideally might want to skip running it on CI when using cargo test.

[calavera]

I don't understand why the workflows didn't run 🤔

ignore

[calavera]

well, I have no idea why GitHub doesn't give me the option to trigger the workflows for your PR. I'll run some tests locally and I'll merge it if everything looks good on my end.

[messense]

I don't understand why the workflows didn't run 🤔

FYI, you removed the pull_request event in 15af83c#diff-5c3fa597431eda03ac3339ae6bf7f05e1a50d6fc7333679ec38e21b337cb6721R1

[calavera]

FYI, you removed the pull_request event in 15af83c#diff-5c3fa597431eda03ac3339ae6bf7f05e1a50d6fc7333679ec38e21b337cb6721R1
oh, I see. I was under the impression that push events were enough. I'll add it back, thanks @messense !

[rnag]

I reverted changes and moved the let final_target up to L60. I think this way it's a few less changes overall.

[calavera]

Thanks @rnag, I'll run local tests again this evening.

[calavera]

This works great now, thanks @rnag !

I'll release a new minor version this weekend with this new feature. Thanks a lot for your help 🤘

[rnag]

@calavera No problem, glad it helps out and I agree it simplifies the build process a bit. I also found a minor issue when doing local testing recently, where if we pass in glibc version in --target then it checks for the wrong target component in the toolchain. I opened a PR #44 to address this.