Remove legacy wal location

What does this MR do and why?

In #325291 (closed) we introduced legacy_wal_location because already scheduled jobs could still contain the legacy database write location in job hash.

In %14.3 we merged !66280 (closed). Now, we can remove this legacy code.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #338213 (closed)