Old API-GW stages aren't cleaned up during deployment.

[richkifvel]

Are you certain it's a bug?

• Yes, it looks like a bug

Is the issue caused by a plugin?

• It is not a plugin issue

Are you using the latest v3 release?

• Yes, I'm using the latest v3 release

Is there an existing issue for this?

• I have searched existing issues, it hasn't been reported yet

Issue description

We made a change to one of our function event paths in our serverless config by adding in {proxy+}
eg:

events:
      - http:
          method: post
          path: api/path

... became...

events:
      - http:
          method: post
          path: api/path/{proxy+}

We found that when this change was deployed to testing accounts, checking in AWS API-GW stages, the old path wasn't removed and the new one was added, which resulted in our tests succeeding.
However when this change was deployed to other accounts the old path had been removed leaving just the new proxy path. We are getting two very different behaviors here, sadly the former resulted in this endpoint not working properly. Do you know what the expected behavior is and if this change should be removing the old path in API-GW stage?

Service configuration (serverless.yml) content

N/A

Command name and used flags

serverless deploy --conceal --verbose

Command output

N/A

Environment information

"serverless": "^3.33.0",
    "serverless-plugin-resource-tagging": "^1.2.0",
    "serverless-plugin-datadog": "^5.33.0",
    "serverless-apigateway-service-proxy": "^2.2.1"

I updated serverless to 3.38.0 and was able to see the same behavior where the old path wasn't removed.