Remove use of deployment_already_running

[leewujung]

This PR removes the use of deployment_already_running from the near real-time flow_raw2Sv since in the latest version of deployment engine that is handled through recipe specification through deployment_concurrency under each flow.

@LOCEANlloydizard @eliascapriles-NOAA - pinging you noth here because I have reverted this once but that got overwritten again when #153 was merged. It'll cleaner if you could do a quick patch to the CPS flows/recipe after @eliascapriles-NOAA finishes up all the downstream work of the workflow (e.g. creating Echoview-compatible NASC files).

The yaml specification looks like:

  raw2Sv:
    deployment_name: raw2Sv
    deployment_concurrency:
      limit: 1
      collision_strategy: CANCEL_NEW
    interval: 5