create "future" engagement state and update business logic

[erincd]

• [ ] any engagement with a date greater than today becomes a future engagement
• [x] every day ANET checks to see if any future engagement dates are now today's date, and sends an autogenerated email letting the person know their future engagement has moved to their drafts section
• [x] future engagements no longer show up under draft tile on home page, or under "Drafts" section on my reports page
• [x] when you save a future engagement, the "This is a DRAFT" report info looks different (see below)
• [x] if you change a future engagement date to be today or in the past (as in someone accidentally clicked the wrong day) then it gets kicked into draft state.
• [x] can't submit future engagements, unless it's also cancelled

[erincd]

When you save a draft, a big box pops up that tells you it's a draft and lists the things you need to do before you'll be able to submit it. Can we customize this for future engagements to make it clearer you've done something different than the usual draft report.

• [x] change "This report is in DRAFT state and hasn't been submitted." to "You've created an upcoming engagement."
• [x] change the font color for above line from red to green
• [x] Change "You can review the draft below to make sure all the details are correct." to "After your engagement has taken place, edit and submit this document as an engagement report."
• [x] Change "The following errors must be fixed before submitting this report" to "You'll need to fill out these required fields before you can submit your final report:"
• [x] remove red block and text around unfilled fields. maybe just black text is fine here.

[erincd]

Email to author when upcoming engagement date becomes today:

Hi [author name],

The date of your upcoming engagement, [Meeting purpose], is today. We've changed this future engagement into a draft engagement report. You can find and edit it by going to the "My drafts" on the "My reports" page, or by clicking here (link).

Best, The ANET Team

[hunterp]

Notes for me on what I need to do: plan to do the future engagements thing.

• [x] add FUTURE to ReportState
• [x] on report.new or report.update
  • [x] if engagementDate > today at midnight, then state = FUTURE
  • [x] otherwise state = DRAFT (unless it's being edited by approver).
• [x] on report.submit
  • [x] you cannot submit a FUTURE engagement for review, unless it is CANCELLED
• [x] update AnetEmailWorker to also check for future engagements
  • [x] update them to DRAFT
  • [x] send an email
• [x] change future engagements home tile to filter on FUTURE
• [x] Changes to report/form
  • [x] when engagementDate > today at midnight, show "This will be saved as a Future Engagement"
• [ ] changes to report/show
  • [x] state = future causes top tex tto say "This report is a FUTURE engagement"
  • [ ] make other changes per erin's comment in ticket.
• [x] grep for all places where we reference DRAFT, PENDING_REVIEW, CANCELLED, RELEASED, etc and ensure we match those cases.

[hunterp]

Screenshot of my proposed "This will create a future engagement" :

Let me know any comments/feedback/etc.

[hunterp]

Screenshot of new Report/Show for a future engagement:

Still more work to do, but wanted to post here for @erincd , @efo-usds , @readywater 's feedback if you have anything.

[efo-usds]

@hunterp YAAAAAAS! This is solid - it shouldn't be red because it is in the future, I'm on board. I would change all language, once a future date is selected, to reflect this. (e.g. "Meeting goal - what do you expect to happen during this engagement?")

[hunterp]

• [x] Need correct color to use to denote future engagement on Report Summary
• [x] Need help on the validatable fields and how to make those not error