chore(lambda): explain to not use Version (#19248)

The `Version` object's documentation was pretty unclear,
and only needed to discourage users from using it.


----

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

Author: rix0rrr

packages/@aws-cdk/aws-lambda/lib/lambda-version.ts

@@ -93,16 +93,17 @@ export interface VersionAttributes {
 }
 
 /**
- * A single newly-deployed version of a Lambda function.
+ * Tag the current state of a Function with a Version number
  *
- * This object exists to--at deploy time--query the "then-current" version of
- * the Lambda function that it refers to. This Version object can then be
- * used in `Alias` to refer to a particular deployment of a Lambda.
+ * Avoid using this resource directly. If you need a Version object, use
+ * `function.currentVersion` instead. That will add a Version object to your
+ * template, and make sure the Version is invalidated whenever the Function
+ * object changes. If you use the `Version` resource directly, you are
+ * responsible for making sure it is invalidated (by changing its
+ * logical ID) whenever necessary.
  *
- * This means that for every new update you deploy to your Lambda (using the
- * CDK and Aliases), you must always create a new Version object. In
- * particular, it must have a different name, so that a new resource is
- * created.
+ * Version resources can then be used in `Alias` resources to refer to a
+ * particular deployment of a Lambda.
  *
  * If you want to ensure that you're associating the right version with
  * the right deployment, specify the `codeSha256` property while