v1.10 backport: Functions that allow marks must also deal with unknown values

[jbardin]

Backport

Backport of #35981

The below text is copied from the body of the original PR.

---

You can't deal with marks in a function without also dealing with unknowns. If AllowMarked is true, but AllowKnown is not, the caller will short-circuit evaluation with an unknown, without being able to deal with marks from all arguments. The cty package can't guarantee that an unknown value contains all possible marks (some functions could alter marks based on the value), but it definitely helps to catch unexpected marks as early as possible during evaluation.

---

Overview of commits

• 1e01124

• c4741dc

• a51be5e

• 651a80f

• 2ae0174

• ac54255

• 04aee4e

• 297972e

[github-actions]

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.