[Issue] Allow ignored columns for mview to be specified at the subscription level

[m2-assistant]

This issue is automatically created based on existing pull request: #29692: Allow ignored columns for mview to be specified at the subscription level

---

Summary (*)

Magento 2.4-develop
Current configuration options for indexer subscriptions are limited - only allowing a table to be specified, rather than specific columns that we may be interested in.
Likewise \Magento\Framework\Mview\View\Subscription has the argument $ignoredUpdateColumns, which by default only includes updated_at. This argument is used to ignore columns for update triggers globally.

This change adds another argument to \Magento\Framework\Mview\View\Subscription to allow for columns to be ignored for a specific view/table combination (i.e. at the subscription level).

Example use-case:
You may wish to subscribe to the salesrule table for a custom indexer (e.g. view id of "my_custom_view"), but with current functionality, this results in a reindex occurring any time an order is placed which had the rule applied, due to the times_used column being updated.

With the following di.xml entries, we can specifically ignore the times_used column for our indexer view:

<type name="Magento\Framework\Mview\View\Subscription">
    <arguments>
        <argument name="ignoredUpdateColumnsBySubscription" xsi:type="array">
            <item name="my_custom_view" xsi:type="array">
                <item name="salesrule" xsi:type="array">
                    <item name="times_used" xsi:type="string">times_used</item>
                </item>
            </item>
        </argument>
    </arguments>
</type>

Examples (*)

1. Add di.xml configuration for an existing view - e.g. cataloginventory_stock:

<type name="Magento\Framework\Mview\View\Subscription">
    <arguments>
        <argument name="ignoredUpdateColumnsBySubscription" xsi:type="array">
            <item name="cataloginventory_stock" xsi:type="array">
                <item name="cataloginventory_stock_item" xsi:type="array">
                    <item name="low_stock_date" xsi:type="string">low_stock_date</item>
                </item>
            </item>
        </argument>
    </arguments>
</type>

2. Set all indexers to update on save (this will remove existing triggers)
3. Set all indexers to update by schedule (this will create triggers again)
4. Observe that updating cataloginventory_stock_item.low_stock_date does not create a record in cataloginventory_stock_cl, but does create records in catalogsearch_fulltext_cl and catalog_product_price_cl

Proposed solution

[m2-assistant]

Hi @engcom-Delta. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.