Associate VariationRange lately with Item portal type.

variation property which comes from Item generates getVariationPropertyList.
VariationRange's property defines variation_property which also generates
getVariationPropertyList

As there is conflict which is not solved by category accessor generation
sorting (which is per property sheet) adding later VariationRange will result
in overwriting accessor for category with own one.

master/bt5/vifib_base/PortalTypePropertySheetTemplateItem/property_sheet_list.xml

 <property_sheet_list>
+ <portal_type id="Item">
+  <item>VariationRange</item>
+ </portal_type>
  <portal_type id="Slave Instance">
   <item>Reference</item>
   <item>SlaveInstanceConstraint</item>

master/bt5/vifib_base/bt/revision

-399
+400
\ No newline at end of file

master/bt5/vifib_base/bt/template_portal_type_property_sheet_list

+Item | VariationRange
 Slave Instance | Reference
 Slave Instance | SlaveInstanceConstraint
 Slave Instance | SoftwareInstance