refactor: displays CAN obligate_by as MM/DD/YY

[fpigeonjr]

Issue

#346

How to test

1. Go to list of cans
2. see obligate_by as MM/DD/YY

Screenshots

Definition of Done Checklist

• OESA: Code refactored for clarity
• OESA: Dependency rules followed
• Automated unit tests updated and passed
• Automated integration tests updated and passed
• Automated quality tests updated and passed
• Automated load tests updated and passed
• Automated a11y tests updated and passed
• Automated security tests updated and passed
• 90%+ Code coverage achieved
• [-] Form validations updated

[fpigeonjr]

added obligate_by and sorted alphebetically

[fpigeonjr]

moved to its own component

[fpigeonjr]

@rajohnson90 didn't think this was a Date

[rajohnson90]

It isn't a date. Already covered this on collab but just writing it down so it's documented.

[johndeange]

I think this PR has the off by one error that we discussed the other day, e.g. in the example a 1 year CAN with an appropriation year of 2023 (10/1/2022) should be valid until 9/30/2023 (according to our current business rules). In this case, when the backend returns 2024, the 2024 fiscal year begins 10/1/2023 and so the obligate by should be 9/30/2023.

[fpigeonjr]

I think this PR has the off by one error that we discussed the other day, e.g. in the example a 1 year CAN with an appropriation year of 2023 (10/1/2022) should be valid until 9/30/2023 (according to our current business rules). In this case, when the backend returns 2024, the 2024 fiscal year begins 10/1/2023 and so the obligate by should be 9/30/2023.

I was scared of this, thanks John for calling this out.

[fpigeonjr]