rip out tls for now

[jaketf]

spoke with @xpositivityx and for now we will move forward with opensearch w/o TLS and fluentbit talking to it with the demo admin user. reasoning being the only way this service will be exposed for now requires kubectl portforward access.

to add back the TLS support and using a more secure username / password for fluentbit has been captured in this issue #31

[WillBeebe]

Looks like it simplifies quite a bit 👍

[chrisghill]

FYI, this might be hard to back out of down the road. Changing these certificates will probably cause the primary nodes to not trust each other, so when we restart a primary it probably won't hit "ready". All primaries will need to be restarted at once.