Elastic-blast

Improvements:

- Default batch sizes for blastn and dc-megablast lead to improved runtimes
- Improve AWS quota check based on the number of vCPUs per instance
- Improved logging of dependent tools

Bug fixes:

- Fixed AWS API calls to select instances on all AWS regions

Note to ElasticBLAST users on GCP
**ElasticBLAST versions prior to 1.0.0 will stop working after January 31, 2023** because they rely on version 1.21 of kubernetes, which will reach its [end of life on the Google Kubernetes Engine on that date](https://cloud.google.com/kubernetes-engine/docs/release-schedule). Please upgrade your installation of ElasticBLAST to its latest version.

Improvements:

- ElasticBLAST on AWS now defaults to the[ faster and cheaper EBS gp3 disk type](https://aws.amazon.com/ebs/general-purpose/)
- ElasticBLAST on GCP now supports all of the [versions of kubernetes offered by Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine/docs/release-schedule)
- ElasticBLAST on GCP defaults to the stable version of kubernetes offered by Google Kubernetes Engine

Bug fixes:

- ElasticBLAST uses GCP's recommended way of dealing with read/write persistent disk
- Long user names no longer cause errors in AWS
- Fixed error caused by APIs not being enabled in GCP

Improvements:
* Query splitting module supports streaming data from cloud buckets
* Improved AWS region validation

Bug fixes:
* Fixed problem when AWS_DEFAULT_REGION is not set
* Bug fixes for --dry-run mode
* --batch-len command line option is recognized

New features:
* A new config parameter `cloud-providers/gke-version` to select Google Kubernetes Engine version, defaults to 1.21

Improvements:
* GCP project config parameter is now optional. If missing elastic-blast will use `CLOUDSDK_CORE_PROJECT` environment variable or the default GCP project set in `gcloud` config.
* GCP zone config parameter now defaults to `us-east4-b`
* Improved error message when persistent disk size exceeds user’s quota

Bug fixes:
* Fixed a persistent disk problem in GCP
* Invalid janitor schedule string does not cause resource leak and is properly reported

Improvements:
* `elastic-blast status` always reports BLAST errors
* BLAST+ updated to version 2.13.0

Improvements:
* `elastic-blast status` updated to report when ElasticBLAST is submitting jobs to the cloud