Core: OO style functions

[iopapamanoglou]

Core: OO style functions

Description

Move core/util.py functions into respective classes (Node, Module, ...)
Improves ergonomics by a lot.

Checklist

Please read and execute the following:

• My code follows the coding guidelines of this project
• My PR title is following the contribution guidelines
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if applicable)
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works (if applicable)
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I ran Black to format my code

Code of Conduct

By submitting this issue, you agree to follow our Code of Conduct:

• I agree to follow this project's Code of Conduct

[mawildoer]

We could trivially generate util functions that maintain the same interface as before, and would avoid breaking designs. That said, I think only Ruben falls into that bucket

@deprecated("Use instance method `nodes_with_trait` instead")
def get_all_nodes_with_trait[T](node: T, trait) -> list[Nodes]:
    return node.nodes_with_trait(trait)

etc....

[iopapamanoglou]

Yeah generally good idea. Had it like that. But deliberately chose to get rid of util.py for good.
This is ofc resulting in a 4.1.0 next release.

[mawildoer]

Is the implication of using a Graph, rather than a Node that you can pre-process it with other filters etc...

[iopapamanoglou]

Yeah, but also node should be only used if we respect the hierarchy.
Since the esphome exporter looks for connected buses this breaks hierarchy and thus is better of using the full graph.