fix: outdated links to production mode docs

[tarekoraby]

No description provided.

[vaadin-bot]

SonarQube analysis reported 4 issues

1. DefaultDeploymentConfiguration.java#L329: Merge this if statement with the enclosing one.
2. AbstractConfigurationFactory.java#L73: Refactor this method to reduce its Cognitive Complexity from 20 to the 15 allowed.
3. DefaultDeploymentConfiguration.java#L305: Replace this lambda with a method reference.
4. DefaultDeploymentConfiguration.java#L309: Remove useless curly braces around statement

[github-actions]

Unit Test Results

   720 files     720 suites   22m 30s ⏱️
5 648 tests 5 598 ✔️ 50 💤 0 ❌
5 664 runs  5 614 ✔️ 50 💤 0 ❌

Results for commit a66c1f1.

[vaadin-bot]

Hi @tarekoraby and @tarekoraby, when i performed cherry-pick to this commit to 2.8, i have encountered the following issue. Can you take a look and pick it manually?
Error Message:
Error: Command failed: git cherry-pick 5ec8ddd
error: could not apply 5ec8ddd... fix: outdated links to production mode docs (#12553)
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add ' or 'git rm '
hint: and commit the result with 'git commit'

[vaadin-bot]

Hi @tarekoraby and @tarekoraby, when i performed cherry-pick to this commit to 2.7, i have encountered the following issue. Can you take a look and pick it manually?
Error Message:
Error: Command failed: git cherry-pick 5ec8ddd
error: could not apply 5ec8ddd... fix: outdated links to production mode docs (#12553)
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add ' or 'git rm '
hint: and commit the result with 'git commit'

[tarekoraby]

@caalador what does the above message by vaadin-bot mean? Does something have to be done?

[caalador]

As we would want to have the link fixed also in 2.7 and 2.8 branches (so vaadin 14) the bot tried to do a cherry pick, but there was some merge issue so it needs to be picked manually.

I can do the pick for this.