Create an InviteService

[rdimitrov]

Summary

The following PR creates an InviteService for verifying and fetching invite metadata

Change Type

Mark the type of change your PR introduces:

• Bug fix (resolves an issue without affecting existing features)
• Feature (adds new functionality without breaking changes)
• Breaking change (may impact existing functionalities or require documentation updates)
• Documentation (updates or additions to documentation)
• Refactoring or test improvements (no bug fixes or new functionality)

Testing

Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.

Review Checklist:

• Reviewed my own code for quality and clarity.
• Added comments to complex or tricky code sections.
• Updated any affected documentation.
• Included tests that validate the fix or feature.
• Checked that related changes are merged.

[coveralls]

coverage: 53.453% (-0.001%) from 53.454%
when pulling 667c018 on invite-service
into 266f0f4 on main.

[JAORMX]

@rdimitrov remember that new services need to be added to the ingress configuration in the helm chart.

[coveralls]

coverage: 53.435% (-0.02%) from 53.456%
when pulling 041188f on invite-service
into 457f6ab on main.

[JAORMX]

is this only the project's display name? don't we want to show the actual project's name or ID?

[rdimitrov]

Display name is enough in this case since this API will be used solely to query invite metadata based on the invite code so the FE can fill things like "X invited you to join Y"

[JAORMX]

And we'd be persisting the project elsewhere, right?

[rdimitrov]

Yes 👍