Testing: Remove condition from 'autosave' e2e test

[im3dabasia]

What?

Closes #58959

Removes the conditional assertion and early return from the "shouldn't conflict with server-side autosave" e2e test.

Why?

• The test contained a FIXME workaround that masked an intermittent issue where server-provided autosave values were occasionally unavailable after reload.
• By removing the conditional escape hatch, the test is now deterministic and properly validates autosave behavior without hiding potential problems.

How?

Removed the stillHasRemoteAutosave variable check.

Testing Instructions

1. Run the autosave e2e tests: npm run test:e2e -- test/e2e/specs/editor/various/autosave.spec.js
2. All tests should pass without errors

Result

• All tests pass without errors.
• While the root cause of the original intermittent issue remains unknown, removing the conditional has not introduced any failures, which indicates the issue was either rare or has been resolved in the current codebase.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: im3dabasia <im3dabasia1@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[Mamaduka]

Hm, not sure about this, test becomes flaky, and there's an annotated failure. That was the main reason I had to introduce the condition.

Try re-running it multiple times locally for testing.

Screenshot