Issue Summary

Changing the default Rovo Agent Scenario doesn't work, without a UI error, and the Trigger data for the soon-to-be default gets erased or needs to be re-entered to continue. 

Steps to Reproduce

1. Visit any Atlassian Cloud instance and try to create a new Rovo Agent scenario (this only works for Customer-created Rovo Agents; it doesn't work for system, Forge, or OOTB)
2. Create a new Scenario and define a trigger, instructions, skill, and the knowledge sources
3. Wait for all of the fields to be saved, then reload the screen to ensure everything was actually saved
4. Activate the Rovo Agent by toggling the option
5. Click Set as default, then confirm

Expected Results

Rovo allows us to save the created Scenario as the new default

Actual Results

The UI doesn't return an error, but it doesn't save the scenario as a new default. In addition, it tends to clear the previous data present in the trigger section for that scenario.

Workaround

Copy the instructions of the current default to the new scenario and adjust the Trigger to ensure this always gets matched. One way of doing that is to adjust the conversation starters and triggers to match: 

1. Adjust the conversation starters to contain a specific word
2. Adjust the triggers of your new default to match that word