ASA: Normalize advisory_classified_hfi table

We now have a run_parameters table that contains unqiue combinations of run_type, run_datetime and for_date. This table is referenced by the high_hfi_area table, but should also be used by the advisory_classified_hfi table so we are not repetitively storing this data in each row.

**Acceptance Criteria**
- [ ] advisory_classfied_hfi has a foreign key reference to run_parameters
- [ ] run_type, run_datetime and for_date fields are removed from advisory_classified_hfi
- [ ] crud operations on advisory_classified_hfi are updated to join reflect the changes

Start by locating the advisory_classified_hfi and run_parameters table definitions, the existing high_hfi_area relationship, and the CRUD operations for advisory_classified_hfi. Compare the current schema and queries with the acceptance criteria, then verify the foreign key, removed fields, and updated join behavior.

Written by the indexing model from the issue text.