Do not always override warning count - provide action to do so

[davenice]

CMCI requests can be subject to a configured "warning count". This is a number of returned records beyond which a request will not be fulfilled and a 403 will be returned.

This is to protect the user from allocating a very large result set on the server accidentally.

The user action in response to the 403 would be either to apply a filter so that fewer records are returned, or to override the warning count (if that's allowed by the server configuration).

Currently the extension always overrides the warning count when making requests.

The extension should make a request without overriding the warning count. If the warning count 403 is returned, a message can be shown with an button to allow the user to make the request again, setting the warning count override parameter.

[github-actions]

Thank you for raising this enhancement request.
The community has 90 days to vote on it.
If the enhancement receives at least 5 upvotes, it is added to our development backlog.
If it receives fewer votes, the issue is closed.