Return pattern and route information for stop deletion

[philip-cline]

Checklist

• [x] Appropriate branch selected (all PRs must first be merged to dev before they can be merged to master)
• [x] Any modified or new methods or classes have helpful JavaDoc and code is thoroughly commented
• [x] The description lists all applicable issues this PR seeks to resolve
• [x] The description lists any configuration setting(s) that differ from the default settings
• [x] All tests and CI builds passing

Description

Return patternId and routeId with stop deletion error so that the front end can link a user to these areas for faster (and much more usable) deletion work flow

[philip-cline]

I am on the fence about unit tests as well, there doesn't seem to be a comparable test already created for cascading deletion scenarios. However, that could be a good reason to create one now maybe... I will defer to the reviewers on that.