Add support for profiling with Scalene

[chuckwondo]

Added a new input (scalene_args) to allow users to run the algorithm via Scalene to produce a profiling (mem+cpu) report. The input value is simply a string of command-line options to pass to scalene to launch the algorithm within the existing subset.sh run script.

In addition, added/modified the following to address various inconveniences along the way:

• Combined/simplified conda lock usage to significantly speed up the build.sh script that installs deps into the conda environment
• Added bin/generate-lock-file.sh script for conveniently regenerating the conda lock file after changes are made to either environment.yml or environment-dev.yml
• Updated algorithm_config.yaml to match new structure/naming implemented on the MAAP API side
• Added convenience scripts for managing algorithm registration, all of which use the updated algorithm_config.yaml file:
  • bin/describe-algorithm.sh
  • bin/register-algorithm.sh
  • bin/delete-algorithm.sh
• Updated docs/MAAP_USAGE.md accordingly

Here are 2 example profile outputs in the ADE, both using the same algo inputs, but one is a "reduced" profile:

• ~/shared-buckets/dschuck/gedi-subset/profile.html
• ~/shared-buckets/dschuck/gedi-subset/profile-reduced.html

[wildintellect]

Interesting, did you manually drop the dates from the release versions? or was that an auto-formatting? isn't against semantic versioning to included - because they seem useful.

[chuckwondo]

I removed them from the file for 2 reasons: (1) each is a guess based on when we think the actual release will be made (so it is possible to be wrong), and (2) they are redundant because github automatically adds the release date to the releases page

[wildintellect]

But that would require a user to go dig into the Github releases and cross reference. It's much nicer to just have it in the log for humans to read.

[wildintellect]

Need to Document what this file's purpose is, comment at top would suffice.

[chuckwondo]

Will do.

[wildintellect]

What's the expected method for executing this script and it's relatives?

[chuckwondo]

The delete-algorithm and register-algorithm scripts are referenced in CONTRIBUTING.md. The describe-algorithm script is not described because it is not really intended to be used directly. The other 2 scripts call it.

[wildintellect]

I made some suggestions and asked a few clarifying questions. Nothing is a blocker that I can see, but I would like the readability for regular users addressed before approving.