Updates to wadm to support wasmCloud 1.0

[brooksmtownsend]

(last updated 3/6 3:48PM EST) wadm builds now and so do the tests, so next step is getting unit tests to work and then moving to integration tests. This will involve making the necessary changes to models to support interface link definitions and configuration, and then for integration tests we'll likely approach the same tests with new application manifests.

(last updated 4/3 9:30PM EST) This PR will test against the first release candidate of 1.0 for wasmCloud, and seek to implement the minimal viable functionality with parity today. I'll create a separate issue to track restoring full integration tests, adding a ConfigScaler, etc.

Feature or Problem

This PR updates wadm to support deploying components, providers, creating links and referencing named configurations inside of links. This required updates to the manifest format itself, detailed below in consumer impact. To sum it up in just a few words, nearly all of the state handling code, control interface interactions, and code related to links needed to change for 1.0 (for the better!) hence the wide variety of changes in this PR.

Related Issues

Filed #253 and #252 as followups.

Release Information

wadm v0.11.0

Consumer Impact

Any consumers of wadm will need to update their manifests to match the new format. Some changes are done in a way that won't be breaking (removing contract_id and link_name from the provider manifest.) The breaking change that developers should pay attention to is in the link.

Previous (wadm 0.10.0) format:

  - type: linkdef
    properties:
      target: httpserver
      values:
        address: 0.0.0.0:8080

New format:

  - type: link
    properties:
      target: hello
      namespace: wasi
      package: http
      interfaces: [incoming-handler]
      source_config:
        - name: httpaddr
          properties:
            address: 0.0.0.0:8080

As of wasmCloud 1.0, links are unidirectional, so the link trait property should go under the component which is the source of the link, and target the other component in the manifest as it did before. Additionally, links are specifically connecting a component or provider's imported WIT function to another component or provider's exported WIT function, so instead of specifying a contract here we specify the namespace, package, and interfaces that will need to be linked.

Testing

Unit Test(s)

Almost all unit tests were modified in order to either accompany new state changes, reduced burden of event handling, or the new manifest format. No unit tests were removed, but I did add a few new ones that handle creating component IDs automatically on behalf of the user.

Acceptance or Integration

Manual Verification

We've manually verified a few working applications deployed with this new wadm on wasmCloud v1.0.0-alpha.4

[thomastaylor312]

Some additional feedback. Unless otherwise noted, the callouts of s/actor/component are optional except for user facing things like the model or public facing documentation. That code will likely be some of the most used (for parsing manifests and other things in the wasmcloud-operator at the least) so that should have things replaced with components