Feature/voyage submission

[cherylli]

Description

Add voyage project submission feature

• table to store submissions (FormResponseVoyageProject)
• controller (POST voyages/submit-project)
• services
• e2e tests
• sample responses

TODO:

• Generate db migration
• Fix broken unit test due to adding new voyage module

Issue link

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature updates / changes
• Tests
• 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

How Has This Been Tested?

Tested manually on swagger and with e2e tests

Checklist:

• 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 tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have updated the change log

[JoshuaHinman]

The e2e tests passed, but I had a problem on swagger. The example request returned 409 for me

[cherylli]

The e2e tests passed, but I had a problem on swagger. The example request returned 409 for me

@JoshuaHinman Thanks for checking this out! That's because I populated the database with seed using voyageTeam1, and each team can only submit the project once. It should work if you use voyageTeamId = 2

Maybe I should change the sample to voyageTeam2

[cherylli]

Updated sample req body to teamId 2, also added a note to the description

[timDeHof]

Looks good!Swagger and tests pass

[JoshuaHinman]

All test passed and swagger responses verified!

[JoshuaHinman]

All good