feat(language): allow tweaking version cache

[JanDeDobbeleer]

Prerequisites

• I have read and understood the contributing guide.
• The commit message follows the conventional commits guidelines.
• Tests for the changes have been added (for bug fixes / features).
• Docs have been added/updated (for bug fixes / features).

[JanDeDobbeleer]

@lewis-yeung .Text can never be taken into account for cross template properties for primary and right, only for extra prompts. The reason is that the execution happens in parallel and writing sequentially. The check looks at if the segment has been executed in case there's a need in a template, but .Text is only available after writing, and thus after that check happens, as needs is a precondition for resolving .Text. Theoretically a check could be built-in that validates the presence of .Text and its value, but that would only work sequentially and in my opinion, that logic isn't worth my while as I don't really see the use case in primary and right.

[lewis-yeung]

@JanDeDobbeleer Got it. I was taking that as an example to reproduce the issue, but not using it in my own config.

[JanDeDobbeleer]

@lewis-yeung It was a really good catch, but that should be the only case where this behavior occurs, which I can live with as "by design". I want to keep that part as simple as possible. If you notice any other behavior, let me know!

[lewis-yeung]

@JanDeDobbeleer Unfortunately, reverting the fix brought back the issue of #2885. It occurs not only when cross-referencing the .Text of a segment, but any property.

[JanDeDobbeleer]

@lewis-yeung I made sure to test this with cross segment properties. I can double check, but this shouldn't be the case though.

[lewis-yeung]

@JanDeDobbeleer It should work in an extra prompt, right? However, I always see the issue when using a cross segment property in the transient prompt, but not with the previous fix of ce02759.