Update upgrade fields on version change

[joshdover]

What is the problem this PR solves?

Non ideal solution to https://github.com/elastic/ingest-dev/issues/1184

We should have a more robust way of ensuring that every ack is delivered.

How does this PR solve the problem?

// Explain HOW you solved the problem in your code. It is possible that during PR reviews this changes and then this section should be updated.

How to test this PR locally

Checklist

• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-07-26T08:20:12.582+0000

• Duration: 41 min 53 sec

Test stats 🧪

Test	Results
Failed	0
Passed	751
Skipped	1
Total	752

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[juliaElastic]

Did some testing with this change and it has some unintended side effects, see here: #2582 (comment)

[jlind23]

Closing this for now.