feat: adding typesense service

[cskiwi]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Template (non-breaking change which adds a template)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• I've built the image and tested it on a kubernetes cluster

Test Configuration:

• Operator Version:
• Kubernetes Version:
• Kubero CLI Version (if applicable):

Checklist:

• I removed unnecessary debug logs
• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I documented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings

[cskiwi]

After further thinking, this might be better as a add-on, what do you think @mms-gianni ?

[mms-gianni]

This seems to me to be a borderline case. Both could be suitable. To make an add-on, we would need a Helm chart maintainer. Bitnami, for example.

But I like this template.