Add AV0110: Prefer composition over class inheritance (#302)

* Add AV0110 guideline

Split from #298.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* Update _rules/0110.md

Co-authored-by: Bart Koelman <10324372+bkoelman@users.noreply.github.com>

---------

Co-authored-by: Dennis Doomen <dennis.doomen@greenchoice.nl>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Bart Koelman <10324372+bkoelman@users.noreply.github.com>

Author: 4 people

_rules/0110.md

@@ -0,0 +1,14 @@
+---
+rule_id: 0110
+rule_category: general
+title: Prefer composition over inheritance
+severity: 2
+---
+Inheritance creates a tight coupling between a base class and its derived classes. Any change to the base class can unexpectedly break derived classes, and the inheritance hierarchy can become difficult to understand as it grows. Composition — building behavior by combining small, focused objects or interfaces — avoids these problems.
+
+Prefer composition when:
+- The relationship is "has-a" rather than "is-a".
+- You want to reuse behavior without exposing or depending on the internals of another class.
+- You need to vary behavior at runtime (e.g. through the [Strategy pattern](https://en.wikipedia.org/wiki/Strategy_pattern)).
+
+**Exception:** Inheritance is appropriate when a true "is-a" relationship exists and when derived classes genuinely extend (rather than replace) the behavior of their base class. Always follow the [Liskov Substitution Principle](https://en.wikipedia.org/wiki/Liskov_substitution_principle) when using inheritance.