Adds back Hitach and Storj storage configurations

[srpomeroy]

Proposed Changes

Adds back the lost storage configuration when we deprecated the ETL Backup docs from the 2.x branch.

docs/install-and-configure/install/etl-backup/etl-backup.md

Lines 131 to 191 in ce23be1

	#### S3 compatible tooling
	<details>
	<summary>Storj</summary>
	Because Storj is [S3 compatible](https://docs.storj.io/dcs/api-reference/s3-compatible-gateway/), it can be used as a drop-in replacement for S3. After an S3 Compatible Access Grant has been created, an example configuration would be:
	{% code overflow="wrap" %}
	```yaml
	type: S3
	config:
	bucket: "my-bucket"
	endpoint: "gateway.storjshare.io"
	access_key: "<STORJ_ACCESS_KEY>"
	secret_key: "<STORJ_SECRET_KEY>"
	insecure: false
	signature_version2: false
	http_config:
	idle_conn_timeout: 90s
	response_header_timeout: 2m
	insecure_skip_verify: false
	trace:
	enable: true
	part_size: 134217728
	prefix: "" # Optional. Specify a path within the bucket (e.g. "kubecost/etlbackup").
	```
	{% endcode %}
	</details>
	<details>
	<summary>Hitachi Content Platform (HCP)</summary>
	Because HCP is [S3 compatible](https://knowledge.hitachivantara.com/Documents/Storage/HCP\_for\_Cloud\_Scale/1.0.0/Adminstering\_HCP\_for\_cloud\_scale/Getting\_started/02\_Support\_for\_Amazon\_S3\_API), it can be used as a drop-in replacement for S3. To obtain the necessary S3 User Credentials, see [Hitachi's documentation](https://knowledge.hitachivantara.com/Documents/Storage/HCP\_for\_Cloud\_Scale/1.0.0/Adminstering\_HCP\_for\_cloud\_scale/Object\_storage\_management/01\_S3\_User\_Credentials#GUID-6DA3811F-FBC5-4848-B47D-B2297F0902B7). Afterwards, follow the example below to configure the secret.
	For `bucket`, the value should be the folder created in the HCP endpoint bucket, not the pre-existing bucket name.&#x20;
	{% code overflow="wrap" %}
	```
	type: S3
	config:
	bucket: "folder name"
	endpoint: "gateway.storjshare.io"
	access_key: "<HITACHI_ACCESS_KEY>"
	secret_key: "<HITACHI_SECRET_KEY>"
	insecure: false
	signature_version2: false
	http_config:
	idle_conn_timeout: 90s
	response_header_timeout: 2m
	insecure_skip_verify: false
	trace:
	enable: true
	part_size: 134217728
	prefix: "" # Optional. Specify a path within the bucket (e.g. "kubecost/etlbackup").
	```
	{% endcode %}
	</details>

[thomasvn]

Thanks for adding back in these storage config options @srpomeroy!

[thomasvn]

@srpomeroy Looks like there is one error being thrown by the link checker

[chipzoller]

Fixed.