🎨 Refactor NAComputation with concrete base classes for every operation and ouput new .naviz format

[ystade]

Description

The tool mqt-naviz purposefully introduces a new textual format that allows to execute operations at a specific time stamp. The current output format of NA computation is not really compatible even though mqt-naviz supports a legacy feature to read in this old format with some caveats.

This issue triggered a wider refactoring of the NAComputation. Its entire structure is refactored. Most importantly, concrete Operation have their own class representation inheriting from some super class. At the end, all operations inherit from the class Op. As part of the refactoring, there is a straight forward way to test whether an operation is of some particular type and then it can be casted to this type.

Checklist:

• The pull request only contains commits that are related to it.
• I have added appropriate tests and documentation.
• I have made sure that all CI jobs on GitHub pass.
• The pull request introduces no new warnings and follows the project's style guidelines.

[ystade]

@burgholzer The tests should run through now and all your feedback should be integrated to the best of my knowledge.

[burgholzer]

Great! Many thanks for addressing this so quickly 🙏🏼
I will have a look later today.

[ystade]

@burgholzer There is (at least) one issue remaining. I used the convention to append a _ to members to avoid name shadowing as suggsted. This conflicts with the naming convention. What do we want to do about it?

[burgholzer]

@burgholzer There is (at least) one issue remaining. I used the convention to append a _ to members to avoid name shadowing as suggsted. This conflicts with the naming convention. What do we want to do about it?

Hm. Probably the cleanest solution would be to adjust the clang-tidy config so that this is not a violation anymore.
In order to not create dozens of warnings for the remainder of MQT Core, one could use a regex where the trailing underscore is optional.

[ystade]

@burgholzer There is (at least) one issue remaining. I used the convention to append a _ to members to avoid name shadowing as suggsted. This conflicts with the naming convention. What do we want to do about it?

Hm. Probably the cleanest solution would be to adjust the clang-tidy config so that this is not a violation anymore. In order to not create dozens of warnings for the remainder of MQT Core, one could use a regex where the trailing underscore is optional.

Apparently, there is a specific key for that option. See the changes from the last commit.

[burgholzer]

Apparently, there is a specific key for that option. See the changes from the last commit.

I am pretty sure that is not what we want, as this enforces the trailing underscore. And I am also pretty sure you do not have the time resources to go through all of MQT Core and change that.

[burgholzer]

Many thanks for working through all the comments.
This is a really clean PR. I like that very much 😌
I just put on some finishing touches in the last couple of commits. Specifically:

• removed two redundant files that were left over from before the last iteration
• added @file docstrings to all new files. (important for getting proper doxygen output)
• completed some missing docstrings
• shortened some existing ones where a one-line brief was sufficient
• adjusted the spacing in headers so that the files don't look so cluttered.
• applied some left-over suggestions in the NA computation.

Once CI is green, I will go ahead and merge this.
I'll also create a new 3.0 Beta release so that it becomes easier to directly rely on this in QMAP.