Fire Behaviour Calculator (old): Evolve 'select-columns' functionality — restrict some columns, set column order

**As a** *(User Type/Persona)* **I want** *(Feature/enhancement)* **So That** *(Value, why is this wanted, what is the user trying to accomplish)*

**Additional Context**
- It doesn't make sense to allow users to hide the Weather Station or Fuel Type columns
- ~the table is basically useless without them. But keeping these columns fixed while maintaining their current L->R order in the table is complicated and beyond the scope of this ticket. So for now, it's a "feature" that users have the freedom to hide columns that provide crucial context as to what they're looking at.~
- ~Also noteworthy is that because the current implementation doesn't maintain the L->R order that columns appear in the table, if a user deselects (hides) a column and then later re-selects it (makes it visible again), that column gets appended to the far right of the table, thereby messing up the order. This bug feature could be fixed as a consequence of implementing a set order for the columns.~

**Acceptance Criteria**
- [ ] Given (Context), When (action carried out), Then (expected outcome)
- [ ] Given (Context), When (action carried out), Then (expected outcome)

**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

The issue names no files, tests, or entry points to start from. Its acceptance criteria are placeholders, so clarify which columns must remain visible and the required order before implementation; done requires agreed criteria and appropriate test coverage.

Written by the indexing model from the issue text.