Unit tests that test location/size before BeginInit() and/or LayoutSubviews() are bogus

[tig]

E.g.

		[Fact]
		public void AutoSize_False_ResizeView_Is_Always_False ()
		{
			var label = new Label () { AutoSize = false };

			label.Text = "New text";

			Assert.False (label.AutoSize);
			Assert.Equal ("{X=0,Y=0,Width=0,Height=1}", label.Bounds.ToString ());
		}

It does not make sense to assume anything about the size or location of label (or any View) without LayoutSubviews() having been called on the view's superview.

This test passes in v1 because when Text is set, OnResizeNeeded (previously called ProcessResizeView) was always called:

		public virtual ustring Text {
			get => text;
			set {
				text = value;
				SetHotKey ();
				UpdateTextFormatterText ();
				ProcessResizeView ();
			}
		}

In v2, we need to use BeginInit/EndInit more cleanly, and code like the above will change to the following which breaks the above test.

		public virtual ustring Text {
			get => text;
			set {
				text = value;
				if (IsInitialized) {
					SetHotKey ();
					UpdateTextFormatterText ();
					OnResizeNeeded ();
				}
#if DEBUG
				if (text != null && string.IsNullOrEmpty (Id)) {
					Id = text.ToString ();
				}
#endif
			}
		}

I will be refactoring any such unit tests as part of #2360 like this:

		[Fact]
		public void AutoSize_False_ResizeView_Is_Always_False ()
		{
			var super = new View ();
			var label = new Label () { AutoSize = false };
			super.Add (label);

			label.Text = "New text";
			super.LayoutSubviews ();

			Assert.False (label.AutoSize);
			Assert.Equal ("{X=0,Y=0,Width=0,Height=1}", label.Bounds.ToString ());
		}

[tig]

This is largely addressed. There may be a few stragglers. If an old unit test is failing and you can't figure out why, consider that you're accessing View properties that should only be accessed after BeginEnd() and/or LayoutSubViews() has been called.