[Fix] Lose OriginatingApp Connection on Save After Create new

[ThomThomson]

Summary

Closes #74400 by fixing a small typo made in #72725. This typo resulted in the originatingApp connection not being severed after the user saved a newly created visualization and had not specifically checked the save as new visualization button.

How to test

• create a new panel from dashboard
• Once you are in the editor, use the modal (save), to save the visualization / lens visualization
• Deselect 'return to...' and save.
• The originatingApp connection should now be lost, and the top nav menu should only display save

Checklist

Delete any items that are not applicable to this PR.

• Unit or functional tests were updated or added to match the most common scenarios

- [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
- [ ] Documentation was added for features that require explanation or tutorials
- [ ] This was checked for keyboard-only and screenreader accessibility
- [ ] This renders correctly on smaller devices using a responsive layout. (You can test this in your browser
- [ ] This was checked for cross-browser compatibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 76a0fba

Build metrics

async chunks size

id	value	diff	baseline
lens	25.0KB	-11.0B	25.0KB
visualize	677.3KB	-7.0B	677.3KB
total		-18.0B

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[stratoula]

LGTM, tested it on Safari 🎈

[LeeDr]

@ThomThomson if you merged to 7.x you should add label v7.10.0.

If you want to include in 7.9.x you need another backport to 7.9 branch. If it were already merged to 7.9 branch last week then the label should be v7.9.0. If it goes in later it should stay v7.9.1.