Produce DEB files for amd64 for openCL and cuda

[snadrus]

Related Issues

DEB files for Curio should include a way to run via a service while setting all the necessary params.
Params are set by updating /etc/curio.env with values for the database and layers.

The script to build debs requires

• to be running in an amd64 environment in the lotus repo's root folder with build tools added.
• Installation of additional DEBs:
  sudo apt-get install dpkg-dev
• the APT repo's private keyfile.

Running the script looks like this:

~/GitHub/lotus$ go run scripts/curio-apt/make_debs.go 0.9.7 ~/my_private_key.asc
 
gpg: key B751F6AC4FA6D98F: "Curio Storage, Inc. (Debian APT Repo Siging Key) <[email protected]>" not changed
gpg: key B751F6AC4FA6D98F: secret key imported
gpg: Total number processed: 1
gpg:              unchanged: 1
gpg:       secret keys read: 1
gpg:  secret keys unchanged: 1
making
copying
dpkg-deb: building package 'curio-cuda' in 'curio-cuda-0.9.7_amd64.deb'.
Processing curio-cuda-0.9.7_amd64.deb...
gpg: using "B751F6AC4FA6D98F" as default secret key for signing
Signed deb curio-cuda.deb
making
copying
dpkg-deb: building package 'curio-opencl' in 'curio-opencl-0.9.7_amd64.deb'.
Processing curio-opencl-0.9.7_amd64.deb...
gpg: using "B751F6AC4FA6D98F" as default secret key for signing
Signed deb curio-opencl.deb
Done. DEB files are in /tmp/curio-apt2577543726

You'll find in the folder:
curio-cuda-0.9.7_amd64.deb
curio-opencl-0.9.7_amd64.deb

At this point, the DEB files need to go to the correct places in the APT repo and the repo needs an update that also must be signed.

Proposed Changes

Additional Info

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

[LexLuthr]

Looks good with some minor suggestions.