docs: update deployment README

[mmalenic]

Closes #242

It turns out zig is still required, even though cargo-lambda prompts to install it, because the RustFunction construct doesn't support interactivity. Could potentially automate this by simulating 'enter' presses to install zig, but I don't think it's a good idea without user input.

Changes

• Swap out rust.aws-cdk-lambda for cargo-lambda-cdk because of slightly better automation when installing rustup targets and building release.
• Update package.json dependencies, including removing @aws-cdk/aws-apigatewayv2-alpha as it's no longer alpha.

[brainstorm]

Could potentially automate this by simulating 'enter' presses to install zig, but I don't think it's a good idea without user input.

An easier way would be to just pipe to which yes... while I see your point, this only runs on our CI so there's no much harm on piping yes if we have it under control? This change is a revert to previous RustFunction construct if I understand correctly? I recall that the newer one had some significant speed benefits for our CI too?

[mmalenic]

This change is a revert to previous RustFunction construct if I understand correctly? I recall that the newer one had some significant speed benefits for our CI too?

This is changing it to the newer one, if you mean the RustFunction we are using in orcabus from this PR?

The other one (i.e, the one being replaced in this in this PR) works too, but I think this one is slightly more configurable from a command exec point of view. They should both be the same speed - there was some other issues in orcabus with multiple compilations of the same package which I don't think are happening here anyway.

[brainstorm]

This change is a revert to previous RustFunction construct if I understand correctly? I recall that the newer one had some significant speed benefits for our CI too?

This is changing it to the newer one, if you mean the RustFunction we are using in orcabus from this PR?

The old one (i.e, the one being replaced in this in this PR) is okay, but I think the new one behaves a bit nicer from a command exec point of view. They should both be the same speed - there was some other issues in orcabus with multiple compilations of the same package which I don't think are happening here anyway.

Ah, okok, sorry, got them mixed, I thought you were reverting here, all good then, merge!

[mmalenic]

Sure, thanks. I'll still try piping yes tomorrow and see what happens.

[mmalenic]

I'm having trouble getting yes to work. I've added a note about using cargo lambda build to install zig, which I think is okay for now. I'm not sure if it's the best idea to automatically install zig without user input anyway, especially because different platforms will have different options (e.g. using brew/pip/choco).

[brainstorm]

Carry on Marko, getting rid of zig cc is a gigantic amount of work: cargo-lambda/cargo-lambda#672