send window width in formplayer query

[Robert-Costello]

Product Description

This is part of the body of work to allow showing different content (forms, menus) depending on the user's screen size.
This example below shows a menu with a display condition that check that the windowWidth is >= 992.
In a real-world implementation there would be another for whose display condition would check that the windowWidth was < 992. That way the menu and forms that are optimized for a particular screen size would be displayed to the user.

Technical Summary

Jira ticket

Feature Flag

no

Safety Assurance

Safety story

this simply sends an additional query param to Formplayer, so is unlikely to cause any issues.
tested locally and will go through QA along with the FP component.

Automated test coverage

no

QA Plan

Rollback instructions

• This PR can be reverted after deploy with no further considerations

Labels & Review

• Risk label is set correctly
• The set of people pinged as reviewers is appropriate for the level of risk of the change

[MartinRiese]

Looks good otherwise

[MartinRiese]

I think I would call it windowWidth to make it clear which dimension it is and also use camelCase for Json

[Robert-Costello]

windowWidth is a good idea. When I started on this it wasn't clear exactly what the value was going to be, but since it turned out to be the actual width, as opposed to a boolean or something else, windowWidth makes sense.

As far as the snake_case goes, I was following what seemed like a standard pattern in FP's SessionNavigationBean which extends InstallRequestBean which extends AuthenticatedRequestBean. That turns out to not be consistent when you look at restoreAsCaseId in AuthenticatedRequestBean so I'm not sure it matters too much. camelCase also doesn't break anything in FP so it seems fine to use.

[MartinRiese]

I was just looking at the line above as reference.