Improve the reinitialize-verity docs. (#366)

1. Add the `Added in v0.17` string to the new API.

2. Update the input image API docs to mention the new
`reinitializeVerity` API.

Author: cwize1

docs/imagecustomizer/api/cli.md

@@ -41,7 +41,9 @@ If verity is enabled in the base image, then:
   [verity](../api/configuration/verity.md) API.
 
 - Otherwise, the existing verity settings are reapplied to the image after OS
-  customization.
+  customization, according to the
+  [.storage.reinitializeVerity](./configuration/storage.md#reinitializeverity-string)
+  setting.
 
   This feature is in preview and may be subject to breaking changes.
   You may enable this feature by adding `reinitialize-verity` to the

docs/imagecustomizer/api/configuration/inputImage.md

@@ -36,7 +36,9 @@ If verity is enabled in the base image, then:
   [verity](verity.md) API.
 
 - Otherwise, the existing verity settings are reapplied to the image after OS
-  customization.
+  customization, according to the
+  [.storage.reinitializeVerity](storage.md#reinitializeverity-string)
+  setting.
 
   This feature is in preview and may be subject to breaking changes.
   You may enable this feature by adding `reinitialize-verity` to the

docs/imagecustomizer/api/configuration/storage.md

@@ -154,3 +154,5 @@ Supported options:
 
 - `all`: During OS customization, all verity data partitions are mounted as read-write.
   The verity hash partitions will be regenerated.
+
+Added in v0.17.