fix(lambda): automatic currentVersion conflicts with explicit Version resource

[comcalvi]

In #23225, we automatically created a currentVersion Version object if the currentVersionOptions property was specified.

However, this breaks the case where a user both:

• Specifies currentVersionOptions
• Never calls currentVersion but instead creates a Version object directly.

In that case, 2 Version resources are created, but the second one fails because Lambda will not allow creating a new Version if nothing changed since the last Version.

Reverting that change.

---

All Submissions:

• Have you followed the guidelines in our Contributing guide?

Adding new Construct Runtime Dependencies:

• This PR adds new construct runtime dependencies following the process described here

New Features

• Have you added the new feature to an integration test?
  • Did you use yarn integ to deploy the infrastructure and generate the snapshot (i.e. yarn integ without --dry-run)?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[gitpod-io]

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
• Commit ID: 6cbae35
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[SamStephens]

@comcalvi it would have been much appreciated if you'd bothered to tag the original issue #23002 in this revert, as I've just wasted a lot of time trying to work out how the fix for that issue ended up being reverted.