Feat/217/v1 commons

[juancwu]

Checklist

Before opening this PR, make sure the PR:

• Has an assignee or group of assignees.
• Is labelled properly.
• Has the SPUR project assigned to it.
• Has an assigned milestone.

Additionally, make sure that:

• My code follows the style guidelines of this project.
• I have performed a self-review of my code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.

Description

• Since we don't have much right now in the backend, just some basic response structs were made.
• A new file was also introduced to put request structs for the v1 package routes.
• Two helpers functions added to help with responding repetitive code branches.

Linked Issues

• Part of [BE Feat] Setup and create common shared data structures and objects #217

Type of Change

Please delete options that are not relevant:

• 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.

Testing

• Test success helper cases: with message, and without message
• Test fail helper cases: with/without message and with/without internal error

[AmirAgassi]

lgtm