Remove refs to Test Migration repo

Author: Donald Booth

docs/best-practices.md

@@ -40,8 +40,6 @@ We recommend to keep Action Groups having single responsibility, for example `Ad
 Althought the Magento Core team and Contributors join forces to cover most of the features with tests, it is impossible to have this done quickly.
 If you've covered Magento Core feature with Functional Tests - you are more than welcome to contribute.
 
-You can also help with MFTF Test Migration to get the experience and valuable feedback from other community members and maintainers.
-
 ## Action group
 
 1. [Action group] names should be sufficiently descriptive to inform a test writer of what the action group does and when it should be used. Add additional explanation in annotations if needed.
@@ -214,4 +212,3 @@ Since the configurable product module could be disabled, this approach is more r
 [merging]: merging.html
 [parameterized selectors]: section/parameterized-selectors.html
 [sections]: section.html
-[MFTF Test Migration]: https://github.com/magento/magento-functional-tests-migration

docs/introduction.md

@@ -52,12 +52,6 @@ Test
         └── ...
 ```
 
-<div class="bs-callout bs-callout-info" markdown="1">
-
-We are actively developing functional tests. Check out the [MFTF Test Migration][] repository.
-
-</div>
-
 ## Use cases
 
 -  Contributor: changes the core behaviour, fixing the annoing bug.
@@ -122,4 +116,3 @@ Follow the [MFTF project] and [contribute on Github].
 [Functional Testing Framework]: https://devdocs.magento.com/guides/v2.3/mtf/mtf_introduction.html
 [MFTF project]: https://github.com/magento/magento2-functional-testing-framework
 [Find your MFTF version]: #find-your-mftf-version
-[MFTF Test Migration]: https://github.com/magento/magento-functional-tests-migration

v2

@@ -0,0 +1 @@
+Subproject commit 3343a82b84e5b25d30e6e39fb3d1aa0d8dc70634