[move-compiler-v2] clean up a few remaining issues in lambda parser/front-end code

[brmataptos]

Description

Various fixes:

• Remove Constraint::NoFunction as it's too broad.
• Make sure there are still errors for all planned unsupported cases
• Fix LambdaLifter case for bound free variable without copy.
• Distinguish between "not supported" and "not implemented" for lambda features.
• Refine lambda test cases to make _ok versions that compile up to "not implemented" errors.
• Add a test case to illustrate the function name aliasing issue ([Bug][move-compiler-v2] function declarations shadow override local variables with same name in function calls #15360), but changed other tests here to avoid it.

How Has This Been Tested?

Usual tests run, showing unchanged behavior on existing code. Tests under /lambda/ without .lambda. config show proper errors generated if to many functions are used. _ok tests now show code working up until "not implemented" errors.

Key Areas to Review

Most complex stuff is in previous PR, but:

• Am I missing some ability cases (e.g., filtering for store and copy properties in captured free variables?
• Are closures with references getting through?
• Do /lambda/storage/*_ok.move tests look like reasonable code to expect from users?

Type of Change

• New feature
• Bug fix
• Breaking change
• Performance improvement
• Refactoring
• Dependency update
• Documentation update
• Tests

Which Components or Systems Does This Change Impact?

• Validator Node
• Full Node (API, Indexer, etc.)
• Move/Aptos Virtual Machine
• Aptos Framework
• Aptos CLI/SDK
• Developer Infrastructure
• Move Compiler
• Other (specify)

Checklist

• I have read and followed the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I identified and added all stakeholders and component owners affected by this change as reviewers
• I tested both happy and unhappy path of the functionality
• I have made corresponding changes to the documentation

[trunk-io]

⏱️ 31m total CI duration on this PR

Job	Cumulative Duration	Recent Runs
rust-move-tests	12m	🟥
rust-move-tests	12m	🟥
rust-cargo-deny	4m	🟩 🟩
check-dynamic-deps	1m	🟩 🟩
general-lints	54s	🟩 🟩
semgrep/ci	48s	🟩 🟩
file_change_determinator	22s	🟩 🟩
permission-check	13s	🟩 🟩
permission-check	6s	🟩 🟩
check-branch-prefix	1s	🟩

_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

[brmataptos]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• [move-compiler-v2] clean up a few remaining issues in lambda parser/front-end code #15365 👈 (View in Graphite)
• [move-compiler-v2] add parser code for lambda types #14792
• [compiler-v2] add test cases for lambda #14791
• [move-compiler-v2] fix #14633: fix error messages for lambdas, identify change points for more complete lambda implementation #14742
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[rahxephon89]

This error message looks a little bit confusing for users (e.g what is a helper function and how it may affect upgradeability). Maybe just remove requires defining a public helper function, which might affect module upgradeability` and just saying it is not supported yet?

[rahxephon89]

Is there a test case for this error?