refactor(misconf): propagate metadata through CF property chain

[nikpivkin]

Previously, Get*Property methods on Resource used resource-level metadata as fallback when a key was absent, so
misconfiguration findings would point to the resource root instead of the actual location in the template.

With metadata propagation through the chain, findings now point to the closest existing ancestor, which is semantically
more accurate.

The old behavior also masked a bug where incorrect property paths silently resolved by skipping
missing components — e.g. ResultConfiguration.EncryptionConfiguration.EncryptionOption would return the value of ResultConfiguration.EncryptionOption if EncryptionConfiguration did not exist.

• GetProperty on Resource and Property now propagates parent metadata to the returned value when a key is absent
• As*Value methods use the property's own metadata instead of requiring it as a parameter

Checklist

• I've read the guidelines for contributing to this repository.
• I've followed the conventions in the PR title.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).
• I've added usage information (if the PR introduces new options)
• I've included a "before" and "after" example to the description (if the PR is a user interface change).