Contentctl

Remove verbose print which could expose sensitive arguments during ACS deploy.

Update how long we wait for the appinspect api to return results.
First, wait for 40 seconds, then check every subsequent second for the results (appinspects always take at least 40 seconds).
This reduces the wait time for an appinspect without creating undue stress on the appinspect endpoint.

The ACS deploy endpoint address was incorrect - causing ACS Deploy command to fail.

This failure has been fixed.

This release brings a number of exciting features and fixes. The most significant are as follows:

- **ACS Deploy Support** - contentctl can now deploy your app directly into your Classic OR Victoria Splunk Cloud Stack! https://github.com/splunk/contentctl/pull/114
- **Enable Specified Searches by Default** - You can now enable a search in your environment by default (instead of disabled by default) on app build time. When this app is deployed, the search will be scheduled to run. To do this, add the following key to your YML: `enabled_by_default: True` https://github.com/splunk/contentctl/pull/116
- **Allow Comments in Searches** - This fixes a bug where comments could be parsed as macros and cause validation failures. Now, you can include inline comments in the search field of your detection YMLs. https://github.com/splunk/contentctl/pull/115

Change enrichment CLI Behavior
New release to power the change from
--disable_enrichment
to
--enable_enrichment

Improve content development/testing performance
This release adds two new features.
First is the --skip_enrichment command which can be used as follows:

contentctl --skip_enrichment validate
contentctl --skip_enrichment build
contentctl --skip_enrichment test

This command line switch overrides the `enrichments` values contained in `contentctl.yml`, enabling contentctl commands to run MUCH faster by optionally disabling enrichment. Enrichment should still be used for final testing and release builds of content.

Second, since test environments take so long to be configured, by default they will be re-used for subsequent tests. This means that a container test environment, once it has been created, will remain running until it is manually terminated. This behavior can be overwritten by setting the option `contentctl_test.yml ---> infrastructure_config ---> persist_and_reuse_container = True`.
Note that if a test container does not exist when a test begins, it will be created. Finally, the presence of additional messages on the command line when running `contentctl test` indicates that this feature is active:

Container [splunk_contentctl_0] has NOT been terminated because 'contentctl_test.yml ---> infrastructure_config ---> persist_and_reuse_container = True'
To remove it, please manually run the following at the command line: `docker container rm -fv splunk_contentctl_0`


If you have made changes to your environment since it was built, such as adding new apps/TAs, OR you have updated any content that is NOT a detection (such as a macro or lookup), then please terminate your container and rerun `contentctl test`. At this time, those artifacts are not reflected into the persistent test environment.