ENH: Iterate on revit parameters instead of Psets

### Enhancement Description

I know, after so many years of development and so complicated code at the end it may sound provocative, but...
Why overall we iterate through all possible properties in all possible Psets assigned to element's type and fight fiercly for each of them to get the value instead of doing it other way around and iterate through parameters of the element and use maps (built-in and user defined) to export their values to proper IFC properties..?
I assume it is a huge overkill and a super complication of the code (as I see currently it is more complex as exporting geometry o_O).
I still haven't even found the place where the exporter maps parameters to properties...

### Revit Version

2024.0.x

### IFC for Revit Addon Version

24.x.x

### Windows Version

10 22H2

No file, test, or entry point is named. Begin by locating the exporter code that maps Revit parameters to IFC properties, then compare the current Pset traversal with the proposed element-parameter approach. The issue does not define acceptance criteria, so confirm the scope and expected mapping behavior before implementation.

Written by the indexing model from the issue text.