[FEATURE] Support update connector without undeploying the model

[zane-neo]

Is your feature request related to a problem? Currently the update connector API checks all the usage of it and only when no model using it, then update operation can go through, but this doesn't seem reasonable, especially for remote models.

1. When remote model deploys, it's an object creation and put into a map: https://github.com/opensearch-project/ml-commons/blob/main/plugin/src/main/java/org/opensearch/ml/model/MLModelManager.java#L1144
2. When connector information changed, the connector information and cached model info can be retrieved, then updating the model in cache should able to redeploy the model with new connector info.

What solution would you like? Adding a new parameter like redeploy_model=true in the url param can reduce the manual effort to undeploy/deploy the model.

What alternatives have you considered? Change the default behavior to automatically redeploy the model after connector updated.

Do you have any additional context? Add any other context or screenshots about the feature request here.