Fix compatibility issues with new backend logs API

What does this MR do?

!18950 (merged) introduced ETag so we can cache the logs results correctly.

This is the frontend adaptation to to changes in this backend API.

• Build a path using Api.getPodLogs which calls a path from the backend.
• Retry after backend has returns 202 - ACCEPTED.
• Re structure the vuex store to hold information needed to make the requests to this new API.

⚠ Note: Turn on this FF to see these changes

`environment_logs_use_vue_ui`

Screenshots

Same old logs page, no visual changes occurred.

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

Related to #33537 (closed)

Closes #36101 (closed)