Limit configs based on ConfigId property

[andrewheumann]

An upcoming pringle PR displays the name (rather than just the dimensions) of layout variants, so a user may select "8P" in a meeting room to get an 8P meeting room. This change revealed some issues:

• because orientation was inconsistent, a different config than the one specified may get chosen.
• because the rooms match the config dimensions exactly, we might actually wind up with the next size down.

This PR creates a pringle-specific pathway based on the existence of the Config Id property on a room, which is only set in Pringle. If this property is present:

• We limit the possible configs to the single one matching the config ID
• We force the orientation to use the first edge of the profile segment as its orientation edge

We also add a small amount of tolerance to the "fit" algorithm, so that an exact size match yields the correct type.

I have tested this on Pringle in an in-progress branch with the Meeting Room type. Other "named" configs for other types are less specific about precisely what you're going to see, so I didn't feel the need to update them, but when re-published they should do a better job of respecting the specified type name as well.

---

This change is 

[anthonie-kramer]

Reviewed 14 of 14 files at r1, all commit messages.
Reviewable status: complete! 1 change requests, 0 of 1 approvals obtained, 1 unresolved discussion (waiting on @andrewheumann)

---

LayoutFunctions/LayoutFunctionCommon/LayoutStrategies.cs line 255 at r1 (raw file):

        {
            // If a set of wall candidate options are provided, limit to the one that aligns with the boundary's first edge.
            // In the future, as room shapes become more editable, we might want to pass in an explicit "orientation edge" instead of just using the first edge.

We could use the PrimaryEntryEdge as the orientation edge

[anthonie-kramer]

One comment below about using the PrimaryEntryEdge on the RoomEdge class as the orientation edge

Reviewable status: complete! 1 change requests, 0 of 1 approvals obtained, 1 unresolved discussion (waiting on @andrewheumann)

[andrewheumann]

Reviewable status: complete! 1 change requests, 0 of 1 approvals obtained, 1 unresolved discussion (waiting on @anthonie-kramer)

---

LayoutFunctions/LayoutFunctionCommon/LayoutStrategies.cs line 255 at r1 (raw file):

Previously, anthonie-kramer (Anthonie Kramer) wrote…

We could use the PrimaryEntryEdge as the orientation edge

I like this suggestion; we'd have to do a bunch of additional work in Pringle to have it create RoomEdge objects etc, so I'll leave as a TODO for now.