Parameter mapping for all Ifc entity attributes

In the current solution, each time we want to use Ifc entity attributes, as Name, LongName, Tag, Description and Classification, we have to point to parameters, with the an Ifc prefix.

This means that our implementation can't use OOTB parameters and map them in the exporter parameter sets.
Double the amount of parameters, because we can't point Mark and Type Mark, to Name. Can't point Comments and Type Comments to Description.
Confuse users that come in, and aren't used to delivering IFC, thinking that something is missing in our setup, change annotations and schedules to the OOTB parameters, or don't even fill them in - and then..

In the end, we have an more verbose and confusing parameter list than needed to, and it's harder to implement IFC centered workflows than needed.

I know this have been brought up several times - but not giving up :)

The issue does not name files, tests, or an entry point. Begin by locating the exporter parameter-mapping code for IFC entity attributes and compare how OOTB Revit parameters such as Mark, Type Mark, Comments, and Type Comments are handled; done means these attributes can be mapped without duplicate IFC-prefixed parameters.

Written by the indexing model from the issue text.