Update reference data for Migration Tests

Update migration tests in master to cover migration from new version. Since 1.18, this step could be done automatically with the following steps. For more information please refer to this page.

1. On the published release tag (e.g., release-1.16.0), run 

   $ mvn clean package -Pgenerate-migration-test-data -Dgenerate.version=1.16 -nsu -Dfast -DskipTests

The version (1.16 in the command above) should be replaced with the target one.

1. Modify the content of the file apache/flink:flink-test-utils-parent/flink-migration-test-utils/src/main/resources/most_recently_published_version to the latest version (it would be "v1_16" if sticking to the example where 1.16.0 was released). 
2. Commit the modification in step a and b with "[release] Generate reference data for state migration tests based on release-1.xx.0" to the corresponding release branch (e.g. release-1.16 in our example), replace "xx" with the actual version (in this example "16"). You should use the Jira issue ID in case of [release]  as the commit message's prefix if you have a dedicated Jira issue for this task.

1. Cherry-pick the commit to the master branch.