We use JAMA for requirements management. You can check their website for more details https://www.jamasoftware.com/platform/jama-connect/

Tessy by Razorcat

Towards python for all generations. Idea is to connect to EA DB in a headless mode using the python interface. Parse the model with python interface and generate new outputs (like xls, xml) using python. Moving away from DLLs (c#). There is nothing wrong with DLLs(C#) with EA15 its even more easier.

We don't have anything concrete now. Working with one of the Sparxs partners on this topic. Idea is for a file based system for the model.

For merging two EAP file, I believe there is already a solution available. Check the session on Lemon Tree by LieberLieber. The idea is not have a eap file in GIT, but a lot of small files mapping to packages in the UML model.
Once a change is made to specific package, then a specific file is updated to GIT.

You are welcome. We connect to EA in a the python interface. You cannot execute python script inside EA. Refer these.
https://www.sparxsystems.com/forums/smf/index.php?topic=589.0
https://blog.httpwatch.com/2019/03/22/how-to-use-python-with-a-com-library-like-httpwatch/

Any xml generation is possible. If the data is modelled properly and consistently generating the xml is possible. I would say generating the xml is the easy part (either though Jscripts or EA addins). The ports (Provided/Required interface) that you add can be easily fetched. They are sub-elements of component element. The provided and required interface are linked to the actual interface. The classifier of the provided interface would point to an actual interface. Once you reach the interface it can be generated in any form.

Yes, LabVIEW but for Integration testing.

For the forward engineering: we develop a high-level SW architecture and then a low-level detailed design. Although in a model it is difficult to separate, but we have largely achieved this partition.

These DLLs are specially developed for our environment and use case.