Added support for wick invoke on app configuration

[jsoverson]

Historically, wick invoke would only work on component configuration, and making individual calls to operations in complex wick apps has gotten more difficult with provides/requires, root configuration, and resources.

This PR adds wick invoke support for application configurations. When you do wick invoke your-app.wick <path::component::operation>, wick will instantiate a runtime and all children scopes, but will not start any trigger logic. It will find the appropriate scope by name and execute the operation in isolation. The deep reference syntax is IDs separated with two colons. E.g.,

$ wick invoke app.wick parent1::parent2::component::operation [same invoke config]

In addition, this PR:

• enables deep invocation support for wick invoke on components for consistency.
• refactors inconsistent, legacy naming in wick-runtime.
• changes the audit/lockdown component syntax from dot-delimited (this.that) to double-semi-colon-delimited (this::that) for consistency.
• changes the __root__ audit/lockdown node to __local__ to align with local Entities.