fix: revert hot_standby change

[shemau]

Description

Issues #508 introduced a regression in wal_level. Revert the wal_level part of that PR.

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• If relevant, a test for the change is included or updated with this PR.
• If relevant, documentation for the change is included or updated with this PR.

For mergers

• Use a conventional commit message to set the release level. Follow the guidelines.
• Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
• Use the Squash and merge option.

[shemau]

/run pipeline

[shemau]

hot_standby was causing a hang in provisioning, so the expectation is the PR pipeline will fail

[ocofaigh]

As per internal discussions, remove wal_level to allow it to default to replica

[ocofaigh]

Super seeded by #514