HCAP-1294 - Phase date range validation

[mmumby]

Work completed

• Added a FE yup validation that checks if the new phase date range overlaps with an existing phase range
• Added validation to the server route to ensure there are no overlaps before POST/PATCH
• Updated test suites - edited mock dates to ensure no overlap, added test cases for creating a phase with an overlap.

New phase form:

Edit phase form:

UI if phase name is very long:

UI if there are multiple long names that overlap - note the user has to intentionally force a large overlap in order to see more than 1 phase in the list. (I added a max height of 250px to the section and a scroll, the scrollbar is only visible when actively scrolling)

https://user-images.githubusercontent.com/25125247/221968762-8a52a018-611b-4e1d-ac66-aa75e5d0119d.mov

UI OPTIONS: (When phase names are long, the dates seem to get lost amongst the words, I've added some bold to see if that's preferrable) This is the current look

[rhattie-ey]

We should merge this after #895 to make resolution simpler.

[mmumby]

@rhattie-ey I'm good with that plan!

[sonarcloud[bot]]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
14.1% Duplication