Improve the accessibilty and visibility of logs from migrations Job

Summary

This issue picks up where #21089 (closed) left off. As the first iteration of migrations-on-Kubernetes, we decided to upload the logs to Elastic, put appropriate search links in our documentation, and links to the documentation in the CI job output. (Discussion thread)

The old setup where we can see logs from the rake db:migrate command in the CI job itself is quite convenient. Moreover, Elastic does not really work well with unstructured logs, which need to be read line-by-line. A part of this issue is to investigate if there is some way to get the logs back into the CI Job from a Kubernetes resource; another question we should try to answer is can we make the experience of single-line logs better in Elastic? (Or more drastically, should the Rake task db:migrate output structured logs? 😅 )

Acceptance Criteria

• Identify whether it is possible to get migrations Job logs into the CI job logs
• [-] Identify whether there is anything we can do (collaborating with #g_observability) to make reading unstructured logs in Elastic more natural => Not required.
• Implement any solutions that are found