Reverse logs display order and scroll hijacking

What does this MR do?

Today when logs are loaded they force the browser to scroll to the bottom, because we display logs chronologically.

Reversing the sort order and removing the scroll hijack results in a better experience, paves the way for infinite scrolling to get historical data (#198050 (closed)) and bring us closer to what our competitors are doing.

It also stops us from loosing access to UI elements in the top of the page as soon as the page loads (such as breadcrumbs and alerts)

Screenshots

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team