Figure out how to handle layout in GlideNode

[sjudd]

See #5230 (comment).

We should verify we're using fixed constraints if they're provided.

If not, ideally we'd find a way of influencing the layout based on the image attributes without overriding fixed constraints and ideally minimizing layout changes when the image or thumbnails load

[sjudd]

I think there are basically three cases here:

1. Fixed size
2. Bounded size (But not fixed)
3. Unbounded size

Each of these may apply to width or height individually, or both.

There's also some demand (#5219, and useIntrinsicSize in Painter) to adjust the layout based on the image (and/or placeholder) size.

I'm currently thinking we should support:

1. Fixed size (preferred)
2. Bounded size
3. Bounded size with useIntrinsicSize
4. Unbounded size.

For (1), we'll use the fixed size for both layout and as the target size for the Glide load.
For (2), we'll use the maximum of the bounded size for layout and the target size for the Glide load. The actually drawn image may be significantly smaller than the bounds depending on the request options. This lets you use scales and transformations that fill a space.
For (3), we'll use the maximum of the bounded size for the Glide load, but we'll layout to 0 by default. If a placeholder is set, we'll layout to use the placeholder's size. When the image (and any subsequent thumbnails) load, we'll use those sizes. This is ok for some limited number of use cases (e.g. #5219), but will cause lots of layout jank in others.
For (4), we'll treat this as a request to use the intrinsic size, and match the behavior for (3).

We'll need to add a useIntrinsicSize option to GlideImage to implement (3).

[sjudd]

I ended up deciding against useIntrinsicSize, I think it differs too much from the Image behavior and it's not super intuitive.

Instead we'll merge (2) and (3) above so that they behave as described, but as if useIntrinsicSize is always true.