Associate VariationRange lately with Slave Instance 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

@@ -7,6 +7,7 @@
   <item>SlaveInstanceContraint</item>
   <item>SoftwareInstance</item>
   <item>TextDocument</item>
+  <item>VariationRange</item>
  </portal_type>
  <portal_type id="Software Instance">
   <item>Reference</item>

master/bt5/vifib_base/bt/revision

-356
+357
\ No newline at end of file

master/bt5/vifib_base/bt/template_portal_type_property_sheet_list

@@ -3,6 +3,7 @@ Slave Instance | Reference
 Slave Instance | SlaveInstanceContraint
 Slave Instance | SoftwareInstance
 Slave Instance | TextDocument
+Slave Instance | VariationRange
 Software Instance | Reference
 Software Instance | SoftwareInstance
 Software Instance | SoftwareInstanceConstraint