Fire page migration - Fire building code

### Page or pages that needs to be migrated:
https://www.austintexas.gov/department/fire-building-code
https://www.austintexas.gov/department/fire/faq

**Note thinking these could be either info page or doc collection?. If we make a collection, refer to the issue for making the Annual Report into an official doc.

- [ ] Create pages using current content types.
- [ ] Make no additions to the text, you may delete redundant text.
- [ ] Log content debt.
- [ ] Note common term usage in the [word bank 'Monstro'](https://docs.google.com/spreadsheets/d/1gEyX6ayn1TW7CQxngsMT9pej-egMWxCtxAzRWXAeLfM/edit#gid=0).
- [ ] Create Github issues (tag as content debt).
- [ ] Record content debt in Joplin notes content debt includes: fact-checking, reading level, length, accessibility, questions about the user or the necessity of this page, user research debt, service design debt, policy lab work, and new features to dev.
- [ ] Move to review and tag another content strategist for review.
- [ ] Reviewer uses [checklist] (https://docs.google.com/document/d/1FVP_ZiQyT2P5F6GUNET327L6hyyexrkA-IzKXQjjzXw/edit#heading=h.7aga879dvzu9) for guidance.
- [ ] Reviewer documents new alpha URL in the department's inventory spreadsheet.
- [ ] Reviewer documents all newly created Contacts, Locations, documents and other snippets, if applicable

**target date: **

Start by reviewing the two source pages: the Fire Building Code page and Fire FAQ, then determine whether they fit the current info-page or document-collection content types. Preserve the existing content while removing redundancy, log content debt in Joplin and the linked word bank, and create any needed content-debt issues. Move the work to review using the checklist and record the alpha URL and newly created items in the department inventory.

Written by the indexing model from the issue text.