eCH-0261 - Branch pruning

[AFoletti]

At GRKDT we began an effort to tidy up a little those eCH repositories. This includes deleting stale or ourdated branches.
The main goal is to have a cleat state to start from using the new policy as described in the readme.

In this ticket I will list the branches that I will DELETE on friday 20.12.2024, along with their owner.

If a branch owner does not want to see his branch deleted, please:

1. Check the branch and rebase it if needed
2. Open a PR, explaining the goal of the branch and pointing to the open issues solved by it
3. Put a comment in this issue.

[AFoletti]

Here the branches I propose to delete:

Branch name	Branch owner	Comment (AFoletti)
improvement/v1/branchingConventions	@montanajava	Obsolete (see new policy in readme)
eCH-0261_typo	@hurni	Obsolete
improvement/v1/updateUmlFor108	@montanajava	No changes from Master
validatable	@montanajava	I don't really understand this branch
schematron-poc	@montanajava	A neat idea but I doubt we will ever implement it in production.
create-samples	@montanajava	I don't really understand this branch
example-diagrams	@montanajava	No changes from Master
Referencing-eCH-0108	@montanajava	No changes from Master

[AFoletti]

No answers. Branches deleted as per above