Update firefly-helm-charts to FireFly 1.3 and KiND deployment

[SamMayWork]

ref: #74

This PR is only a slight change from the core of the PR above with the following differences:

• Deploys FireFly 1.3
• Does not directly mirror the Besu helm charts from an external provider, they're now cloned at deploy-time and applied to the cluster

[EnriqueL8]

Looking good - quite a few tweaks needed

[SamMayWork]

In discussion w/ @EnriqueL8 - there's a quite a few comments from the original PR around the app versions that we're using in these charts, this mostly appears to be leftovers from the original PR, but something that we need addressing.

Problem: Right now we're not specifying a specific tag for the images that we're using for FireFly components, this means that we're defaulting to latest which might stop working at some point we don't know.

The solution we're proposing is the following:

• This PR contains the images for FireFly 1.3.0
• When this PR is merged, we cut a release of this repository which contains only the 1.3 images
• A GitHub action is added which does some basic testing of the stack using KiND
• On a regular cadence we update the images that these charts are using and then cut a new release each time

Automation to make the above easier is certainly possible and would be a meaningful contribution to this project.

[SamMayWork]

In reference to specific comments about things in the chart that aren't in the stack we're intending to use, for example AWS/Azure/Geth...

It looks like parts of the values chart that we're using come from documentation from things like Besu and purposefully have multiple values so that they're unopinionated as possible, but not sure we want that here. Essentially, these helm charts now have 2 parts: deployment of chain infrastructure, and deployment of FireFly. For chain infrastructure we want to be very opinionated so that we don't break our KiND installation path, but our FireFly helm charts must be unopinionated.

With that in mind, I'm going to make this PR very restrictive WRT which chain infrastructure we deploy.

[SamMayWork]

From comments here by @EnriqueL8 it looks like this PR being merged creates a few new items to make things here easier/more resilient:

• Automated testing of the chart through a GitHub actions (checking that components deploy properly, with maybe some basic integration testing).
• Hardening around the multiparty script using the status APIs to ensure that the nodes change through states as expected
• Script to add and manage new keys into the deployed FireFly
• Verification of the multiparty scripts against new APIs introduced into FireFly since 1.3 was released

I'll open these issues once this PR is merged

[SamMayWork]

OK - Calling this PR good for a re-review, it's worth noting that currently this is not going to work because of this issue hyperledger/firefly-dataexchange-https#81, once a release has been properly cut, I'll retest this PR and we should be good for a merge.

[EnriqueL8]

I've just ran this locally

W0628 12:24:56.735297   28761 warnings.go:70] unknown field "spec.automountServiceAccountToken"

Error: An error occurred while checking for chart dependencies. You may need to run `helm dependency build` to fetch missing dependencies: found in Chart.yaml, but missing in charts/ directory: firefly-evmconnect

[EnriqueL8]

It would be nice if we could configure the swagger urls to be the port forward URL so that the swagger UI works with FireFly

We exposed a configuration in FireFly to allow this https://hyperledger.github.io/firefly/latest/reference/config/#http

We could also think about deploying an ingress instead of port-forwarding as it's such a common thing

Update: already available in the values.yaml would be good to automatically set that as part of the set of commands that get printed after helm upgrade

[EnriqueL8]

Having a small tutorial on how to push to the kind registry a custom image would be amazing as well, doesn't need to be part of this PR

[EnriqueL8]

We will hold off until 1.3.1 goes out and we will get this in!

[EnriqueL8]

Awesome, looks good to me now that the images have been updated