fix panic about float in storage port, and add a test that verifies it
Merge pull request #501 from natefinch/fix-1347715

fix panic about float in storage port, and add a test that verifies it

So, this __fixes-1347715__ - at least the most problem thing to crop up.  We have tests in the code that were checking to make sure that if a float gets into the config via json deserialization, that we handle it correctly.  However, it wasn't doing precisely the same thing the production code does, so it wasn't actually getting the value into the right area of the environConfig, and wasn't actually calling storagePort().  The test I added does this, and I verified it fails with a panic with the old code for manualConfig... then fixed the code the do a type assertion first, handling float64 and int... reran the test and now the test passes.

My only concern is that I don't know what changed to cause this error to suddenly start occurring.  I'm going to look into it and see if I can find the change that revealed this error.
Cleaned up manual provider float storage port test

Avoid copying an existing test and just extend the existing one
that tests the same scenario.
Revert PR 449

PR 449 by @voidspace breaks CI, restore is using StatePort
so all restore related tests break.
Reverting until we find a solution so it does not block
CI
Merge pull request #503 from perrito666/revert_PR_449

Revert PR 449

PR 449 by @voidspace breaks CI, restore is using StatePort
so all restore related tests break.
Reverting until we find a solution so it does not block
CI
this fixes-1355324
Merge pull request #502 from mjs/float-storage-port-test

Cleaned up manual provider float storage port test

Avoid copying an existing test and just extend the existing one that tests the same scenario instead.
Actions CLI - tracer implementation

Just connects the command line 'actions' and 'do' to the apiserver