ENH: Category mapping ifc version consistency

### Enhancement Description

The current implementation of the Category Mapping UI allows the users to mix 2x3 and 4.3 ifc classes in the mapping table, and is not related to the target version set in the export config. I would suggest to bind these mapping templates to specific ifc versions, and only allow ifc classes that are available in that version. On the config form the specified ifc class should affect which category mapping templates are available for that config.
I understand that it would be too complicated to handle this issue in the type and instance mappings, but at least the configured category mapping should behave like this.

### Revit Version

2025.4.x

### IFC for Revit Addon Version

25.4.0

### Windows Version

11 24H2

Trace the Category Mapping UI and export configuration form to see how IFC versions, mapping templates, and available IFC classes are currently selected. Verify the supported classes for each IFC version and how the configured target version reaches the form; done means category mappings cannot mix versions and the config exposes only compatible templates and classes.

Written by the indexing model from the issue text.