[ENH]: add push_logs() to log interface

[codetheweb]

Description of changes

Does what it says on the tin.

Test plan

How are these changes tested?

• Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

n/a

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[codetheweb]

• [ENH]: add push_logs() to log interface #3576 : 2 dependent PRs (#3577 , #3590 ) 👈 (View in Graphite)
• [CLN]: split up log impls into separate files #3575
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[codetheweb]

Merge activity

• Jan 28, 7:36 PM EST: A user started a stack merge that includes this pull request via Graphite.
• Jan 28, 7:39 PM EST: Graphite rebased this pull request as part of a merge.
• Jan 28, 8:26 PM EST: A user merged this pull request with Graphite.