Update regex in ControllerAclTest

[aleron75]

Description

Change regex in ControllerAclTest::getControllerPath() to avoid classes which are under a namespace with a "Controller" part (like for example controller plugins) being interpreted as controllers causing the Act test to fail.

I need this change because, in the scope of MSI development, I have to define the following plugin for a controller:

    <type name="Magento\Catalog\Controller\Adminhtml\Product\Initialization\StockDataFilter">
        <plugin name="allow_negative_min_qty"
                type="Magento\InventoryCatalog\Plugin\Catalog\Controller\Adminhtml\Product\Initialization\StockDataFilter\AllowNegativeMinQtyPlugin"
                sortOrder="1"/>

The Magento\InventoryCatalog\Plugin\Catalog\Controller\Adminhtml\Product\Initialization\StockDataFilter\AllowNegativeMinQtyPlugin plugin class makes the test fail because it is considered a controller but doesn't extend \Magento\Backend\App\AbstractAction.

Manual testing scenarios

• define a plugin on a controller declaring it under a namespace with a "Controller" part
• run the ControllerAclTest static test
• expect the test to fail

[magento-engcom-team]

Hi @aleron75. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento-engcom-team give me test instance - deploy test instance based on PR changes
• @magento-engcom-team give me {$VERSION} instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

[orlangur]

LGTM, but you need apply changes to 2.2-develop first.

[aleron75]

Created PR #16707 fir 2.2-develop, thanks

[magento-engcom-team]

Hi @orlangur, thank you for the review.
ENGCOM-2275 has been created to process this Pull Request

[magento-engcom-team]

Hi @miguelbalparda, thank you for the review.
ENGCOM-2275 has been created to process this Pull Request

[magento-engcom-team]

Hi @aleron75. Thank you for your contribution.
We will aim to release these changes as part of 2.3.0.
Please check the release notes for final confirmation.