fix: catch NoSuchEntityException in InvalidSkuProcessor for bundle products

[kapil971390]

Description

InvalidSkuProcessor::retrieveInvalidSkuList() calls productRepository->get($sku) without catching NoSuchEntityException for bundle products. If a bundle product is deleted between the initial retrieveProductIdsBySkus() lookup and the repository fetch, the exception propagates uncaught and fails the entire POST /V1/products/base-prices batch.

Fixes #40882

Root cause

// Before — no exception handling
if ($allowedPriceTypeValue
    && $type == \Magento\Catalog\Model\Product\Type::TYPE_BUNDLE
    && $this->productRepository->get($sku)->getPriceType() != $allowedPriceTypeValue
) {
    $valueTypeIsAllowed = true;
}

BasePriceStorage always passes $this->priceTypeAllowed = 1 as $allowedPriceTypeValue, so this code path is reached for every bundle product in a batch.

Fix

Applied the same try/catch pattern used in ACP2E-4998 (TierPriceValidator::checkQuantity()):

if ($allowedPriceTypeValue
    && $type == \Magento\Catalog\Model\Product\Type::TYPE_BUNDLE
) {
    try {
        $product = $this->productRepository->get($sku);
        if ($product->getPriceType() != $allowedPriceTypeValue) {
            $valueTypeIsAllowed = true;
        }
    } catch (NoSuchEntityException $e) {
        // Product was deleted between the ID lookup and repository fetch.
        // Treat as invalid SKU so the rest of the batch continues.
        $skuDiff[] = $sku;
        break;
    }
}

Related

ACP2E-4998 fixed the same pattern in TierPriceValidator::checkQuantity() but InvalidSkuProcessor was not updated at the same time.

Test plan

• POST /V1/products/base-prices with a batch containing a bundle product that is deleted concurrently — should report the SKU as invalid and continue processing the rest of the batch
• POST /V1/products/base-prices with only valid bundle products — no behavior change
• POST /V1/products/base-prices with only simple products — no behavior change (code path not reached)

[m2-assistant]

Hi @kapil971390. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.
❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[kapil971390]

@magento run Unit Tests, Static Tests, WebAPI Tests

[kapil971390]

@magento run Static Tests

[kapil971390]

All tests passing. Re-triggering CLA check.