feat: Add AWS lambda support for IPV6 outbound connections in VPC

[Martijn02]

Allows VPC-enabled Lambda functions to use an egress-only internet gateway to access the internet or other AWS services via IPv6. This eliminates the need for a NAT Gateway, reducing costs and simplifying architecture.

Note that this change is fully backwards compatible. It only adds an optional parameter to the VPC configuration.

The credits for the code change itself should go to @rvaralda who created a pull request for the original serverless project.

[mnapoli]

Thanks!

[mnapoli]

Doh I got bit by the new GitHub pull request UI I think… They don't display clearly that the CI did not run (already reported it at https://github.com/orgs/community/discussions/143787?sort=top)… So I merged thinking the CI was green, but actually tests are failing.

I will revert this PR and re-release.

[GrahamCampbell]

I don't think it's a UI issue, it's a CI config issue.

[GrahamCampbell]

Oh, it was the first PR restrictions that stopped the CI running.

[mnapoli]

Yeah, I can't find the exact link again but essentially the new "merge experience" is green and is much much less obvious that the CI is waiting for approval before running. Makes you think the build passed.

I disabled that new UI but somehow it turned back on. Disabled it again, it's not the first time I make this mistake.

[Martijn02]

I don't quite understand what's happening with this. Is there anything I can or should do to help this along?

[mnapoli]

I've had to revert the PR because it broke the tests on master: https://github.com/oss-serverless/serverless/actions/runs/12465150115/job/34790457936

The next step would be to reopen the PR again with working tests.