DcSIFExportEnv no longer has ambiguous constructor overloads

custom.dataCatalog.builder removes the ambiguous DcSIFExportEnv constructor overload pair that previously accepted the same overall argument set with catalogCodeOverride and useInFile in conflicting positions.

This fixes a compile-time problem for downstream subclasses calling super(...), where CET could report an ambiguous function error unless the caller forced the overload with a positional null.

class DcSIFExportEnv

The duplicate public constructor shape has been removed. The remaining constructor places catalogCodeOverride last, after fileRule3D and fileRule2D.

Removed: public constructor(str baseFileName, str[] priceLists, Url outputDir,
                            DataCatalog catalog, str preferredLanguage=null,
                            bool allowAlternateLanguage=true, str productCatalogKey=null,
                            str catalogCodeOverride=null,
                            bool filterProductsByCatalog=true,
                            bool exportMaterials=false,
                            bool renderGMaterials=false,
                            bool exportMaterialResolutions=false,
                            bool exportModels=false,
                            bool ignoreUndefined=true,
                            bool includeOFDAParams=false,
                            bool useInFile=false,
                            bool generateSifSafeFeatures=false,
                            bool fixProductRootMultiGraphics=false,
                            <str, bool, str, bool> fileRule3D=null,
                            <str, bool, str, bool> fileRule2D=null)

Supported constructor:
public constructor(str baseFileName, str[] priceLists, Url outputDir,
                   DataCatalog catalog, str preferredLanguage=null,
                   bool allowAlternateLanguage=true, str productCatalogKey=null,
                   bool filterProductsByCatalog=true,
                   bool exportMaterials=false,
                   bool renderGMaterials=false,
                   bool exportMaterialResolutions=false,
                   bool exportModels=false,
                   bool ignoreUndefined=true,
                   bool includeOFDAParams=false,
                   bool useInFile=false,
                   bool generateSifSafeFeatures=false,
                   bool fixProductRootMultiGraphics=false,
                   <str, bool, str, bool> fileRule3D=null,
                   <str, bool, str, bool> fileRule2D=null,
                   str catalogCodeOverride=null)

If your subclass constructor previously passed a positional null only to disambiguate catalogCodeOverride, you can remove that workaround and call the remaining constructor shape directly.