Explain when *lifting* works and when it doesn't

[nyxz]

File: content/docs/iac/concepts/inputs-outputs/apply.md

In the Inputs/Outputs docs there is the following:

An easier way to access deeply nested properties is by using lifting. Lifting allows you to access properties and elements directly from the Output itself without needing apply.

Then after the example the section finishes with

This approach is easier to read and write and does not lose any important dependency information that is needed to properly create and maintain the stack. This approach doesn’t work in all cases, but when it does, it can be a great help.

I agree the approach is easier to read and write and I'd like to understand when I can or cannot use it.

[nyxz]

I just found this open issue that's related #9779

[jkodroff]

Per @Frassle (I'm summarizing):

Lifting is usually automatically handled by the underlying type system, so it's transparent to the user. You may occasionally experience runtime errors with lifting, depending on what language you are using. For example, in TypeScript an output may resolve to undefined, so using lifting to reference outputThatResolvesToUndefined.someProperty would cause a runtime error.

(We'll add these in a note to the docs to resolve this issue.)