/api/1.x/parameters/profile/{{name}} gives incorrect response for non-existent profiles

[ocket8888]

The endpoint at /api/1.x/parameters/profile/{{name}} will return a 200 OK success and empty "response" array for profiles that don't exist. The proper response to a request for a non-existent resource is a 404 NOT FOUND. Besides this, an empty response array from this endpoint normally indicates that a profile has no parameters, and so tools/admins may subsequently attempt to assign parameters to said profile, which will confusingly and inevitably fail.

[moltzaum]

related: #2940

[rawlinp]

This is possibly going to be fixed by #3098.

[moltzaum]

FYI: #3098 did not fix this issue

[mitchell852]

1.x is going bye bye soon. closing this.