Adding paid event routes

[EthM370]

Adding paid events plugin with get and single attribute update functionality.

[devksingh4]

1. please write unit tests along with the code
2. we camel-case our routes so that its consistent - so for example /api/v1/paidEvents/merch - lets try to rewrite those names

Overall good start though!

[EthM370]

All pending integration and lint issue fixed, still need to write unit test

[devksingh4]

1. for some reason almost every file was changed? What's going on here? Maybe line endings?
2. we want to enforce that every parameter, variable, etc is camel case
3. we should be making our route names "RESTful" where you take an action on a resource (see https://restful-api-design.readthedocs.io/en/latest/ for a decent overview)

Let's talking before/during/after all-hands maybe?

[devksingh4]

For example, an "event" is fundamentally the resouce, a type of which is "paid". So we should be designing our API to be able to take a given action based on whether it's paid or not in our existing price, not making it a different module as "paidEvent"

There's a nice way to do conditional validation in Zod, where we can say "Hey, if it's a paid event then we need these additional parameters, otherwise we don't. (colinhacks/zod#938 (comment)) I would refine it so that there is a base set of parameters that all needs, and then there is a refined model which is what all paid items need. the overall body is the z.union([base set, refined set]). If some attribute from the refined set exists, then we're creating a paid event. This helps us integrate the paid events setup into our existing events route, without building a new route that will cause confusion by the API consumer.