Fix duplicate Price Calculation Setup insert in Shopify pricing integration tests

[Copilot]

Integration tests in codeunit 139605 (Shpfy Product Price Calc. Test) share persistent database state. UnitTestCalcPriceTestNewPricing inserts a Price Calculation Setup record with Code [1-1-10]-7002, and the subsequently-added UnitTestCalcPriceUsesCurrentWorkDate attempts to insert an identical record, causing a duplicate key error at runtime.

Changes

• LibraryPriceCalculation.Codeunit.al — Added FindOrAddSetup: an idempotent variant of AddSetup that filters by Method/Type/Asset Type/Implementation and returns the existing record's Code if found, otherwise delegates to AddSetup.

  procedure FindOrAddSetup(var PriceCalculationSetup: Record "Price Calculation Setup";
      NewMethod: Enum "Price Calculation Method"; PriceType: Enum "Price Type";
      AssetType: Enum "Price Asset Type"; NewImplementation: Enum "Price Calculation Handler";
      NewDefault: Boolean): Code[100];
  begin
      PriceCalculationSetup.SetRange(Method, NewMethod);
      ...
      if not PriceCalculationSetup.FindFirst() then begin
          PriceCalculationSetup.Reset();
          exit(AddSetup(PriceCalculationSetup, NewMethod, PriceType, AssetType, NewImplementation, NewDefault));
      end;
      PriceCalculationSetup.Reset();
      exit(PriceCalculationSetup.Code);
  end;

• ShpfyProductPriceCalcTest.Codeunit.al — Replaced AddSetup with FindOrAddSetup in both UnitTestCalcPriceTestNewPricing and UnitTestCalcPriceUsesCurrentWorkDate so neither method fails when the setup record already exists from a prior test in the same integration test run.