Use Systemd Journal API for all logs endpoints in API

[sairon]

Proposed change

Replace all logs endpoints using container logs with wrapped advanced_logs function, adding possibility to get logs from previous boots and following the logs. Supervisor logs are an excetion where Docker logs are still used - in case an exception is raised while accessing the Systemd logs, they're used as fallback - otherwise we wouldn't have an easy way to see what went wrong.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (which adds functionality to the supervisor)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes RFC: Extend Logging to allow Selecting/Limiting entries and Follow mode #3309
• This PR is related to issue:
• Link to documentation pull request:
• Link to cli pull request: Add flags for handling features of advanced logs cli#471

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Ruff (ruff format supervisor tests)
• Tests have been added to verify that the new code works.

If API endpoints of add-on configuration are added/changed:

• Documentation added/updated for developers.home-assistant.io: Document new logging endpoints in Supervisor API developers.home-assistant#2124

[mdegat01]

Mostly minor comments although there is an issue with the addon logs one that requires some tweaks, see the comment below.

[home-assistant]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[sairon]

This PR should also address this older RFC: #3309

[mdegat01]

Looks great 👍

[agners]

This is changing the content type from binary to text. Are the current users (probably only frontend?) able to handle this?

Supervisor logs are an excetion where Docker logs are still used - in case an exception is raised while accessing the Systemd logs, they're used as fallback - otherwise we wouldn't have an easy way to see what went wrong.

I guess the reverse can be true to. But yeah, since we try journald logs first, it will just not be noticeable in this case.

[sairon]

This is changing the content type from binary to text. Are the current users (probably only frontend?) able to handle this?

Yes, frontend doesn't really care about the content type. Host logs used text in the previous version as well, now it's consistent for all .../logs endpoints.

I guess the reverse can be true to. But yeah, since we try journald logs first, it will just not be noticeable in this case.

I expect the journald erros to be rather persistent (until a reboot, etc.) than intermittent. And Docker logs are used only as the fallback, so if it also fails, you're done :)