Document the 404 behavior of log.get_as_bytes() #1103

log.get_as_bytes() (_resource_clients/log.py:67, async at :175) behaves like get() on a 404, but its docstring leaves out the caveat that get() has: a 404 becomes None only when the client targets a log by ID (client.log(run_id)), while a chained client (run.log()) raises. Copy the note into both docstrings.

✍️ Drafted by Claude Code