[FEAT] Shared application improvements

[brooksmtownsend]

Sharing application components, e.g. linking across different wadm applications, was added in #381. There's a suite of improvements that I considered but decided to omit from the initial experimental release of the feature to gather feedback.

• Report on the status of a shared component, so that you can view shared component statuses with wash app status
• Ensure that a shared application that has dependent applications can't be undeployed or deleted (without a --force or undeploying/deleting the dependents)
• Ensure that deploying a new version of a shared application with dependent applications doesn't remove a component that is depended on
• As @joonas pointed out in feat: support shared components and providers #381 (comment), it would be great to have a reporting option / query to be able to find out all dependent applications of a particular application, or perhaps even a full tree.

I didn't want to over-validate scenarios because the use cases can get complicated for automating the deployment/rollout of shared providers. For right now, the above validations have to be done externally