NEW FireBAT : Map -> Preview Page !!SPIKE!!

**As a** *FBAN/FBS* **I want** *a preview screen* **So That** *the RWCO can review the FBA before printing it or saving it to pdf.*

**Additional Context**
- see [Figma PDF Model](https://www.figma.com/file/AUhBnTB50dnY7ysoxBSqPN/FireBAT-2021?node-id=1082%3A133)
- There is an area for capturing text relating to the FBA - this may imply we are dealing with two screens - screen 1) capture information and screen 2) display advisory preview / print.
- There may be future requirements around who has rights to view and edit the FBA.
- There are concerns around the rendered FBA changing on the fly - which would cause it to differ from the final PDF.
- Think in terms of 3 separate screens. Screen 1: Edit, Screen 2: Read only, Screen 3: System dialog print preview
- Screen 2 and Screen 3 are really the same page, but in print mode, the styles are slightly different. Screen 2 is rendered with CSS making it a normal web page. Screen 3 is rendered with CSS that renders it appropriately for printing.
- For the "print" screen, we want to use the simplest possible formatting. The goal is to get it to print correctly, not bother about how it displays on different sized screens etc.!

**Acceptance Criteria**
- [ ] Given I am on the landing/input screen and want to create an FBA, When I click on "Preview FBA", Then I am taken to an FBA Preview screen.
- [ ] Given I am on the "Preview FBA" screen, When I look at the screen, I can see the table, advisory text and map, no fields are editable/modifiable.
- [ ] I can print it to pdf using the browser - and it seems promising as an approach. (It does not have to be perfect! Just promising)
- [ ] TIMEBOX 2 days.
- [ ] New tickets are to be written based on the output of this. (see #1505 - it should be updated based on findings)

**Definition of Done**
- [ ] Ready to Demo in Sprint Review
- [ ] Does what I have made have appropriate test coverage?
- [ ] Documentation and/or scientific documentation exists and can be found
- [ ] Peer Reviewed by 2 people on the team
- [ ] Manual testing of all PRs in Dev and Prod
- [ ] Merged