SSF-153 Volunteer Create Order Endpoint

[Juwang110]

ℹ️ Issue

(https://vidushimisra.atlassian.net/browse/SSF-153)

📝 Description

This PR adds an endpoint for volunteers to create a new order. There is a lot of criteria going into this route with lots of checks and side effects, the ticket details what I mean.

There were a decent amount of new routes that had to be added for this functionality to work. Here is the list:
/create-multiple in allocations
/associated-donations, /all, /set-quantities, in donation items
/match-all in donations
/create in order

✔️ Verification

I tested functionality of all backend routes with Postman and I also wrote and made sure all tests passed.

🏕️ (Optional) Future Work / Notes

As a note, there are no tests for allocations, and no service tests yet for donation items. These will be added in a future ticket.

[amywng]

r1

[amywng]

last few nits and a note of consideration @sam-schu @Yurika-Kan : the order create method does 4 db operations across 4 different tables but if one of the steps fails then the db could reflect a partially updated state (e.g. reservedQuantities aren't set but orders are made, or donations aren't matched). i looked into it and we could maybe wrap this in a transaction so that all operations succeed or are rolled back/fail. thoughts?

[sam-schu]

Thanks for making separate service functions to better organize the logic not directly related to orders! What was the rationale for making endpoints corresponding to all of those service functions?

Also, agreeing with @amywng that using a transaction to make the database updates all-or-nothing is a great idea

[amywng]

one small nit but other than that LGTM!!!

[sam-schu]

After discussion with Dalton related to using this PR as an example for using a transaction in another PR, we realized it's a bit hard to keep track of whether we're using the default repo, manager, etc. or the one from the transaction. Can we prefix any of these variables/params (for manager, repo, etc.) that come from the transaction manager (if one is provided) with transaction so it's easier to tell that we didn't accidentally use the default one rather than the transaction one somewhere?

[sam-schu]

Can we also give the repos that are coming from the transaction manager the transaction prefix?