Rephrase the deprecation notice that is raised when calling the label() method of a view without an explicit label

Thanks for opening this. First question: what are the pros/cons of triggering the deprecation when label() is called vs. when the view is saved?

My $0.02:

The main pro is that you'll know sooner if you have an invalid view; label() is more likely to be called in the normal course of things than preSave(), especially for views that don't change frequently.

The main con is that label() is a strange place to put the deprecation, because indeed, you really shouldn't be able to save a view without a label.

To me, the conclusion is that both places should trigger the deprecation, with slightly different wording in each.

The main pro is that you'll know sooner if you have an invalid view

+1

Moving to active as consensus seems to be this is a good task to have.