[Change notice] Change more public properties to protected in ViewExecutable and ViewStorage

We talked about this on IRC, but for the benefit of this issue;

This could be pretty tricky at the moment, as the config entity controller uses Reflection to save all the public properties from ViewStorage into config. This was one of the reasons we made $executable protected when we split the classes and add a getExecutable to access it.

Great cleanup! I kind of dislike that we have to first store a variable before using !empty but that's life.

I was confused about this patch (a little bit more context in these patches for people no on the VDC team would be helpful), but tim explained in irc that Views is trying to move away from being able to use $views->foo directly, both for proper refactoring of Views UI, as well as for translatable stuff, etc.

I asked why it was onyl covering a couple of things ('name', base_name') rather than everything and was told that it's because it's focused only on the public properties of a view for now. Further clean-up will happen in subsequent patches.

Since this is just basically a find/replace job, looks good here. I confess I didn't check each hunk individually but I'm guessing any issues will expose themselves pretty fast. ;)

Committed and pushed to 8.x (minus a hunk about the code that was committed as part of #1810826: Remove obsolete form code from views_ui/admin.inc). Thanks!

For more information as to why this issue was moved to the Drupal core project, please see issue #3030347: Plan to clean process issue queue

Moving back to the contributed Views issue queue and closing as outdated per https://www.drupal.org/project/views/issues/3030347#comment-13023447