Allow force update of published API Version / Plan Version config

[msavy]

Description

Apiman imposes immutability on configurations of published APIs and Plans.

This is to ensure that API publishers cannot silently alter the contract established between the API publisher and API consumer (e.g. change rate limits without telling consumer). A new version is usually required.

However, there are some situations where forcing a configuration update may be more appropriate, such as updating endpoints or fixing config mistakes.

It may be that we can use the Apiman event and notification system to alert users that a configuration has been changed?

For some deployments, just updating silently may be OK.

Is this something you are interested in? Which scenarios should we support?

Please comment in this ticket and let me know.

Acceptance Criteria

None yet, but will add some here if/when this becomes a priority