Inconsistent comma separated values in pset template definitions

Some pset template definitions use comma separated values with spaces for their applicable entities, like so:

```
Pset_SpaceFireSafetyRequirements --> 'IfcSpace, IfcSpatialZone, IfcZone'
```

Others do not:

```
Pset_ConcreteElementGeneral --> 'IfcBeam,IfcBuildingElementProxy,IfcChimney,IfcColumn,IfcFooting,IfcMember,IfcPile,IfcPlate,IfcRailing,IfcRamp,IfcRampFlight,IfcRoof,IfcSlab,IfcStair,IfcStairFlight,IfcWall,IfcCivilElement'
```

The example given in the documentation does not use spaces.

I propose to remove all spaces in comma separated lists. Ping @berlotti @TLiebich @aothms

The issue does not identify a file, test, or entry point; begin by locating the pset template definitions and the documentation example referenced in the report. Compare the applicable-entity lists across those definitions, then verify that the agreed comma-spacing convention is applied consistently and that the example remains aligned.

Written by the indexing model from the issue text.