Update QAction documentation for RN44420

[BramDevlaminck-Skyline]

Update QAction documentation with the changes from DCP261954, RN44420

Also added documentation on how to debug reoccurring SLScripting and SLProtocol crashes and how to pinpoint which element is causing the crashes. From the code we will put a link to this page, which in this PR will also have a SLProtocol section. This should make it easy for customers to get to the right procedure depending on if they have an slscripting or slprotocol crash

Wait with merging this change until the mentioned task/RN are merged.

[MariekeGO]

Would it be useful to also add some information about this (and possible a link to the new info) here: https://docs.dataminer.services/dataminer/Administrator_guide/DataMiner_Agents/Configuring_a_DMA/Configuration_of_DataMiner_processes.html#setting-the-number-of-simultaneously-running-slscripting-processes?

[LaurensMT]

There is a typo in the file name: SLScripring instead of SLScripting

[BramDevlaminck-Skyline]

@MariekeGO, as the troubleshooting steps for a reoccurring SLProtocol and reoccurring SLScripting crash are almost identical, I reused the same file, and just referenced that file twice from the toc.yml. I'm not sure if this is something that has been done before, or if you have any objections against this. It would also be OK for me if this is split up, but that would introduce a lot of duplication.

If you have a better alternative that still keeps a good structure without having to duplicate the whole file, that would also be OK

[MariekeGO]

@MariekeGO, as the troubleshooting steps for a reoccurring SLProtocol and reoccurring SLScripting crash are almost identical, I reused the same file, and just referenced that file twice from the toc.yml. I'm not sure if this is something that has been done before, or if you have any objections against this. It would also be OK for me if this is split up, but that would introduce a lot of duplication.

If you have a better alternative that still keeps a good structure without having to duplicate the whole file, that would also be OK

The same file should never be referenced twice in the toc.yml, as this will cause odd behavior that users may experience as a bug. What we usually do in a case like this is add the information in one place, and then add a cross-reference to that place where appropriate, as duplicate information is indeed to be avoided.