Detect and address MVP vulnerabilities - Stage 1

The feature is descoped as a result of discussions in PI planning and suggestions from Alan Giorgio Gerhard and others.

The main focus in PI9 should now be on
1. Test setup or procedure to reproduce SKB14

2. Analysis of causes for SKB14 including going on to any root causes including architectural / timing conditions

3. If feasible in time box of about 3 FPs a fix to remedy the bug, else a path to the same in PI10

4. Learning outcomes should be documented both from architectural / code guidelines and testing approach

This is now estimated at 3FPs, this also accounts for some collaboration time from others apart from the team owning the feature.

 Please also see the comments from Giorgio and Peter on SKB-14 and the discussions in the Slack channel

https://skasoftware.slack.com/archives/C01FYQAPPQV

The Original description has been moved as Clone Feature SP-1488 for PI10, retained here for guidance only

-----------------------------------

As the MVP has grown significant functionality has been added. However it is likely that significant vulnerabilities may exist, including intermittently occurring bugs due to race conditions etc. SKB13 and SKB14 which are under analysis are recent ones.

The goal of this enabler is to analyse for any shortcomings, including the outcomes from the post mortem of earlier bugs, improve the testing to ensure that we can detect more vulnerabilities that exist; and to refactor or bug fix as needed with the goal of improving the robustness of the MVP.

This is expected to be an ongoing exercise across the next few PIs For PI9 we would like to time-box this to about 5 FPs and address the outcomes from SKB13 and 14 plus the first cases of test cases and fixes.

-------------