Rename AgaviViewTestCase Assertions to something more explicit

[felix]

The assertions in the AgaviViewTestCase? imply that they act on the full response object whereas the actual scope is on the data set by the view only. Examples:

• assertResponseHasContentType
• assertResponseHasHeader
• assertResponseHasCookie

Those should be named clearer, maybe

• assertViewSetsContentType
• assertViewSetsHeader
• assertViewSetsCookie

which would make clear that the scope is on the view and not the global response.

See #1113 for an example.

[felix]

(In [4160]) - Renamed assertions in the View to better reflect their scope.

* assertResponseHasRedirect => assertViewRedirects * assertResponseHasNoRedirect => assertViewRedirectsNot * assertResponseRedirectsTo => assertViewRedirectsTo * assertResponseHasContentType => assertViewSetsContentType * assertResponseHasHeader => assertViewSetsHeader * assertResponseHasCookie => assertViewSetsCookie * assertResponseHasHTTPStatus => assertViewResponseHasHTTPStatus * assertResponseHasContent => assertViewResponseHasContent * assertForwards => assertViewForwards

- Changed the unit tests accordingly. - Made the message in assertHasLayer() configurable by the user

fixes #1114