improvement: init spock security context

[kevinpthorne]

Before this PR

init-spock job could not run in a hardened, restricted k8s namespace

After this PR

init-spock runs under a restricted security level by default, with editable values.

[kevinpthorne]

I have a feeling I shouldn't have bumped the version. I'll revert those changes too

[kevinpthorne]

Tested on my local cluster ✅

[kevinpthorne]

the init job is failing due to not being able to authenticate with the rw host. Looking into why -- hoping its not related to this change.

[kevinpthorne]

I had a bad hba config - this looks like it works:

🎯 Configuring Spock for nodes:
 - 🖖 Node: test-data | Hostname: pgedge-cluster-test-data-rw
🔎 Found clusters in namespace pgedge: ['pgedge-cluster-test-data']
✅ All CloudNativePG clusters in namespace ready
✅ pgedge-cluster-test-data-rw is accepting connections
👤 Creating user pgedge on test-data
🖖 Created spock node test-data on pgedge-cluster-test-data-rw
🎉 Spock configuration successfully updated