Events v2: Add some first structure for new events

[rikukissa]

Client

src/v2-events - this is where all events related views and their dependencies should be created or copied

Gateway

src/v2-events - all queries, mutations and other related should be built here

Events

New service that handles storing and reading events. Assumes user authorisation is done in gateway

[github-actions]

Oops! Looks like you forgot to update the changelog. When updating CHANGELOG.md, please consider the following:

• Changelog is read by country implementors who might not always be familiar with all technical details of OpenCRVS. Keep language high-level, user friendly and avoid technical references to internals.
• Answer "What's new?", "Why was the change made?" and "Why should I care?" for each change.
• If it's a breaking change, include a migration guide answering "What do I need to do to upgrade?".

[ocrvs-bot]

Your environment is deployed to https://ocrvs-7869.opencrvs.dev

[makelicious]

Good stuff, comments on ordering of things

[makelicious]

We could keep validation and routes in different files

[makelicious]

Could we get this by getRecordByTransactionId or does the method change hold significance?

[rikukissa]

Good point 👍 Or even just the id:, right?

[makelicious]

We might want to define these as globals. something like this might be close

export default defineConfig({
  test: {
    globals: true,
    }
});