Reporting/Improve Alert on Submit page if BORO ID is not issued

#### Description:
BORO ID must be on the industry users report before they can submit it. IF a user has started a report before a BORO ID has been issued to them and then the ID was issued, then they must go back to the Review Operation Information page and sync the page so the BORO ID appears in their report.

#### Acceptance Criteria:

Given that I am an industry user on my submission page,
If my operation has been issued a BORO ID but the BORO ID is not appearing on the final review page
Then I will see an alert "**Missing BORO ID:** Go to Review Operation Information and click "Sync latest changes from administration" to resolve this."
hyperlink "Review Operation Information" with the corresponding page of the report.

[Wireframe](https://www.figma.com/design/LsDmLDCdnJqI8UahyqvOD8/BCIERS-Designs?node-id=36746-6623&t=9OiDQ4ahiNk3uBhH-4)

#### Development Checklist:

- [ ] Checklist item
- [ ] Checklist item
- [ ] Checklist item
- [ ] Meets the DOD

#### Definition of Ready (Note: If any of these points are not applicable, mark N/A)

- [ ] User story is included
- [ ] User role and type are identified
- [ ] Acceptance criteria are included
- [ ] Wireframes are included (if required)
- [ ] Design / Solution is accepted by Product Owner
- [ ] Dependencies are identified (technical, business, regulatory/policy)
- [ ] Story has been estimated (under 13 pts)

#### Definition of Done (Note: If any of these points are not applicable, mark N/A)

- [ ] Acceptance criteria are tested by the CI pipeline
- [ ] UI meets accessibility requirements
- [ ] Configuration changes are documented, documentation and designs are updated
- [ ] Passes code peer-review
- [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
- [ ] Ticket is ready to be merged to main branch
- [ ] Can be demoed in Sprint Review
- [ ] Bugs or future work cards are identified and created
- [ ] Reviewed and approved by Product Owner

#### Blocked By/Blocking

#### Notes:

-

Start at the industry user's submission/final review page and trace the corresponding Review Operation Information page. Use the acceptance criteria and linked wireframe to verify the missing-BORO-ID alert and its report-specific hyperlink when the ID is absent. Confirm the alert directs users to sync the latest administrative changes and test the behavior through the CI pipeline.

Written by the indexing model from the issue text.