Enhance autoInit job to check for uninitialized vault first

In their testing cyber reported that upon upgrades the autoInit job always runs and fails/errors when the vault installation has already been initialized and unsealed. We would like this job to stay enabled so customers don't have to enable/disable depending on if it's a brand new installation so before any Initialization or Unseal tasks are ran via the job, we should check if the vault installation is already initialized/unsealed first.

AC:

• Add logic to check for initialized/unsealed status to autoInit job
• Test upgrades in dev cluster to verify that on helm upgrade of existing vault installation the job completes successfully and the vault installation is still healthy/active/useable/etc
• New Package tag with changes created
• Above tag merged into BigBang