fix: sam build fails when layer logicalID shared across stacks

[aahung]

Which issue(s) does this change fix?

fix #2724

Why is this change necessary?

sam-cli does not support resolving intrinsic functions in parameters/outputs, which results in incorrect layer reference when the layer is passed from some other stacks using intrinsic functions.

Before we have a great support of intrinsic functions, customers should still be able to build their stacks. Incorrect resolution of layers should only affect local *.

How does it address the issue?

Delay the validation process and only raise exception when certain layer properties are used.
I added two integration tests to cover both using parameters (pass down) and outputs (pass up).

*pass up: template-pass-up.yaml, pass down: template-pass-down.yaml

• pass up before:
  • sam build works,
  • sam local invoke works
• pass up now:
  • sam build works,
  • sam local invoke: Error: {'Fn::GetAtt': ['ChildApp', 'Outputs.LayerVersion']} is an Unsupported Intrinsic works
• pass down before:
  • sam build failed with invalid layer arn error
  • sam local invoke failed with invalid layer arn error
• pass down now:
  • sam build works
  • sam local invoke failed with invalid layer arn error

What side effects does this change have?

for the "pass up" case, customers won't be able to local invoke anymore. This should be the expected behavior.

Checklist

• Add input/output type hints to new functions/methods
• Write design document (Do I need to write a design document?)
• Write unit tests
• Write/update functional tests
• Write/update integration tests
• make pr passes
• make update-reproducible-reqs if dependencies were changed
• Write documentation

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

[aahung]

this was originally here, just reverting

[aahung]

just discussed with @mndeveci, for the change that prevents local invoking a function containing unresolvable layer, the risk is unknown and the benefit does not justify the risk. I just reverted that part and use a LOG.debug instead.