Use the word "name" instead of "label" for display modes

On #2042807: Convert search plugins to use a ConfigEntity and a PluginBag I did a survey of "What do we call the administrative label of things?". I looked at "things" such as Image styles, Content types, Views, and Display modes, where an admin can create multiple "things" and each one needs an administrative label as well as a machine name.

In most cases, the administrative label is called a "name". So for instance, on admin/structure/views, the column header on the table of views is "Name", and if you are creating a view, the edit field label is "View name". For node content types on admin/structure/types, the table column header is "Name", and if you are editing one, the field is also labeled "Name". For image styles on admin/config/media/image-styles, the table column header is "Style name", and when you are editing one, the field is called "Image style name".

Then in all cases, there is also a "machine name" that gets generated automatically from the "thing name", which means you have a "thing name" and a "machine name", and it seems pretty consistent.

But when you're looking at View modes or Form modes, the table header is Label and the edit field is called Label, while the machine name is still called "machine name". It's just a small cognitive disconnect -- it doesn't match what other parts of Drupal are using, and you have "machine name" vs. "label".

So my suggestion is to change the column headers on
admin/structure/display-modes/form
admin/structure/display-modes/view
to say "Name" and the edit field titles when you are editing to say "View mode name"/"Form mode name". Or on the edit screen, it could just simply say "Name".