Fixes for lotus-provider, and conveniences

[snadrus]

Related Issues

FilOzone/Space-Panthers#11

Proposed Changes

• make install now installs lotus-provider
• configuration provides more defaults
• cli tester for windowpost

Additional Info

For testing, these top-level commands (flags available):
lotus-provider test window-post here
Good for: CLI testing to ensure configuration layers & basic functionality work as expected.
Does not post to chain.

lotus-provider test window-post task
Good for: E2E testing of a lotus-provider that's enabled for the window-post task.
Does not post to chain.

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title is in the form of of <PR type>: <area>: <change being made>
  • example: fix: mempool: Introduce a cache for valid signatures
  • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
  • area, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps
• If the PR affects users (e.g., new feature, bug fix, system requirements change), update the CHANGELOG.md and add details to the UNRELEASED section.
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[magik6k]

Some nits / Qs

[magik6k]

Might be nice to have a way to submit a mock-compute task to the database, so the computation isn't done in the local cli, but on the real workers (which imo is what SPs will expect in most cases - running check tasks on the cluster with proper scheduling, but no submitting things to the chain)

[snadrus]

that makes sense. Would you want it to do that with live updates, or just direct them to logs and database to evaluate the success?

[magik6k]

We could have either this or a separate command poll for success

[rjan90]

It would be nice to add these to the default config, as they are needed for getting lotus-provider configured, but are currently missing from the basic config.toml:

[Addresses]
MinerAddresses = [ "MyMinerID"]

[Apis]
ChainApiInfo = ["myJWT"]

[magik6k]

Some more problems here

[magik6k]

This is objectively better, just two small things to fix

[magik6k]

(also some conflicts)

[snadrus]

I'm going to propose a different CLI:

lotus-provider test window-post task
and
lotus-provider test window-post here

That is a bit clearer on what's going on with the two test commands, and provides an avenue for future integration test behavior.

As a side-note, I also made it possible to have titled sql files since I was starting to get lost in all of them. I didn't persist the titles to the database because that seems pointless as it's a developer convenience that doesn't really have an analog at runtime.

[magik6k]

1 think likely to fix, but this PR does make a lot of things better enough to merge now