[Forwardport] Add integration tests for product urls rewrite generation

[rostyslav-hymon]

Original Pull Request

#13567

Adding integration tests for the product url rewrites generation.

Description

This pull request contains integration tests for the product url rewrite generation. We were trying to fix the permanent redirection issue when updating an url_key at store level (see the related issues below).

The issue was caused by $this->urlPersist->deleteByData being executed before the replace process.
We discovered that, in the 2.2-dev branch, the issue was fixed by side effect in this commit: a0d3a63. This PR just provide the tests we were using when fixing the issue but the fix itself is already merged (see: a0d3a63#diff-4e1fd4e484fc5142fc23f8ef0cde6718L53).

Fixed Issues

Related to

• Permanent 301 redirect is not generated when product url changes on storeview scope #13240 (comment)
• Magento don't create product redirect if URL key on store view level was changed. #10073

Maybe related to

• After upgrade to 2.1.3 url rewrite problem multi store #8227
• URL Rewrite issues occur very often /catalog/product/view/id/711/s/product-name/category/16/ #5863
• Permanent Redirect for old URL missing via API #8957

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)

[sunilk4y]

Is there any patch available to fix this issue, or we have to keep waiting for 2.3.0 (
any tentative date for 2.3.0 release?
We have more than 1,000 products with urls like this https://www.makevana.com.au/catalog/product/view/id/4827/s/gold-plated-sterling-silver-clover-leaf-earrings/category/226/ and its very annoying and hurting indexing.

[PiroozMB]

@sunilk4y they don't just care about you and me. They're making fun of us and making money for themselves. You can never find a correct way of fixing their bugs in old versions and they leave people with no answer. very selfish.
@rostyslav-hymon

[miguelbalparda]

@PiroozMB you are acting like a customer and you are not entitled to that in an OSS. Somebody put their effort to fix this in their own free time and you are complaining because you just feel like it. If you need a patch before it’s officialy released you can get the diff and apply it manually via CLI. Just add .diff to any pull request URL and you’ll get the raw diff.

[PiroozMB]

@miguelbalparda which .diff are you talking about. you see on git thousands threads about this issue and each of them has its own diff. by the way if you are not official magento evelopers and you put this as a solution here on git and you haven't tested it not knowing that it's not working!

[wasim-bajwa-rltsquare]

Facing the same issue in magento 2.2.5 version. Also checked the later versions 2.2.7 and 2.3 as well, the issue is still there.

[cygnet-jmcharadva]

Facing the same issue with magento 2.3.1 version. Is there any solution?