[PR #110/ac1351a5 backport][stable-1] Fix exos_config:save_when when a stopped process is present

[patchback]

This is a backport of PR #110 as merged into main (ac1351a).

SUMMARY

NOTE: This is distinct from Bug #109, which I filed earler!

When a stopped process exists on the Switch, the prompt for the save command changes. This trips up save_when, which does not recognize the prompt and it runs into a timeout.

commit message:

When a process is created, and then terminated but not deleted, the
save config prompt will change. This module expected the old prompt,
which never arrived, so the save will run into a timeout.

This is how the special prompt looks:

• Slot-1 HOSTNAMEHERE.1 # save
  The configuration file primary.cfg already exists.
  Some process has been terminated/stopped. If you save the configuration
  then that process's configuration will be lost.
  Do you want to continue? (y/N)

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

exos_config

ADDITIONAL INFORMATION

---
- hosts: all
  connection: network_cli
  user: uedvt359
  vars: 
    ansible_network_os: exos
    
  tasks:
  - name: create a process and make sure it was started at least once
    exos_config: 
      commands:
      - create process testProcess python-module __future__ start on-demand vr VR-Mgmt
      - start process testProcess
      save_when: changed

  - name: stop the saved process
    exos_config: 
      commands:
      - terminate process testProcess forceful

  - name: this will fail, since the prompt is unexpected
    exos_config:
      save_when: always