Remove unintended SpiceDB connection test from constructor

[wscalf]

PR Template:

Describe your changes

• I had added a minimal version of Add logging for spicedb connection on startup #109 locally to help repro Add waits for ready probes in e2e tests #112 and seemingly accidentally pushed it. This PR is intended to revert it.

Ticket reference (if applicable)

Fixes #

Checklist

• Are the agreed upon acceptance criteria fulfilled?

• Was the 4-eye-principle applied? (async PR review, pairing, ensembling)

• Do your changes have passing automated tests and sufficient observability?

• Are the work steps you introduced repeatable by others, either through automation or documentation?

  • If automation is possible but not done due to other constraints, a ticket to the tech debt sprint is added
  • An SOP (Standard Operating Procedure) was created

• The Changes were automatically built, tested, and - if needed, behind a feature flag - deployed to our production environment. (Please check this when the new deployment is done and you could verify it.)

• Are the agreed upon coding/architectural practices applied?

• Are security needs fullfilled? (e.g. no internal URL)

• Is the corresponding Ticket in the right state? (should be on "review" now, put to done when this change made it to production)

• For changes to the public API / code dependencies: Was the whole team (or a sufficient amount of ppl) able to review?

[app-sre-bot]

Can one of the admins verify this patch?

[lennysgarage]

/lgtm

[Rajagopalan-Ranganathan]

/lgtm