Unify plugin errors
What needs to be modeled?
The current error cases SCPluginAlreadyRegisteredErrorResponse and SCPluginRouteAlreadyRegisteredErrorResponse differ only very little, it makes more sense to unify them in one error.
Why is a new model necessary?
The way they are used in the backend makes it more reasonable to use one error with different messages.
Dependencies, issues, features that need to be resolved beforehand
Edited by Jovan Krunić