Collaborate with service design to identify what COAM elements need to be in reports

#### Describe the task

Only at a higher-level, we don't expect to get detailed with this since COAM is still being defined. Will refine after a chat with PO.

#### Acceptance Criteria

- [ ] first
- [ ] second
- [ ] third

#### Additional context
COAM tile will be locked until ~September, so the compliance obligation is the final determined amount that is in the annual report when reporting period ends.

- [ ] If a supplementary report or edited report is submitted after May 31 that resulted in a changed compliance obligation, it will create a penalty in COAM
- [ ] tbd

- From Patricia: "for now, let's make sure their is a link back to the main dashboard from the "submitted" page.
I'm thinking about the situation where users come in and submit a report BEFORE the deadline (like submit on May 5th) and then come back in and make changes and resubmit etc. We don't want them going to COAM before May 31st just in case they make changes to their reports before that. So for now, I think the priority is to send them back to the main page. But we could have some simple language explaining that after May 31st they will need to go into COAM with their total emissions from the compliance summary page. But I'd like to know (maybe via user testing) if showing that compliance summary again, after submission, in the reporting module would be helpful for users. Happy to chat more though!"