fix(bc): better handling of default values

[MartinBelthle]

This pull request significantly enhances the management of default values when using the create_binding_constraint and update_binding_constraint commands. It also addresses an issue with updating terms of a binding constraint using the update_binding_constraint command.

Corrections have also been made to the CommandExtractor class, which extracts commands from a base study and a modified study through comparison, and to the CommandReverter class, which reverses commands based on a command history.

The generation of a study from a list of commands has been corrected: now, the generation stops as soon as an error is encountered, making it easier to identify the failing command, as it is necessarily the last one executed.

[laurent-laporte-pro]

I don't know where those __getattribute__ comes from, but it is a bad practice. We should use getattr() function instead.

[MartinBelthle]

modify the constraint term to remove optional values

[MartinBelthle]

There's an issue with the removal of constraint terms.

[MartinBelthle]

@laurent-laporte-pro I've checked your commit and I think you should revert it because you missed this part of the code that makes your test fail inside the old match function in create_binding_constraint:

    simple_match = self.name == other.name
    if not equal:
        return simple_match

So IMO we should not touch at this code as it would mean a big refactoring for other commands and we do not want that in this PR

[laurent-laporte-pro]

@laurent-laporte-pro I've checked your commit and I think you should revert it because you missed this part of the code that makes your test fail inside the old match function in create_binding_constraint:

    simple_match = self.name == other.name
    if not equal:
        return simple_match

So IMO we should not touch at this code as it would mean a big refactoring for other commands and we do not want that in this PR

I've done a rollback + refactoring. It's OK now.