* Update dependencies

atmosphere-runtime: 2.2.13.vaadin3
jsoup: 1.14.3

* Update Atmosphere version in Constants.java

Co-authored-by: Anna Koskinen <Ansku@users.noreply.github.com>

* Small updates to servlet container test setup.

- Upgraded to use cargo-maven3-plugin since cargo-maven2-plugin is now
EOL.
- Defined supported packagings as the current jetty-maven-plugin default
only covers war.
- Changed a test pojo to implement Serializable in order to prevent an
error in cargo-maven3-plugin stop-container phase.

* Added logging for generateArchetype in BuildHelpers

* servlet test reference screenshots

Chrome 94 screenshot changes

* fix incompatible method used for python script in 7.7

* Update GeneratePostPublishReport.py

* Update Vaadin7 to use atmosphere-runtime 2.2.13.vaadin2

* Update Constants.java

* Chrome 94 (#12434)

* Added logging for generateArchetype in BuildHelpers

* Chrome 94 screenshot changes and version number

Co-authored-by: Olli Tietäväinen <ollit@vaadin.com>

vaadin.com/pro does no longer have the info

* Add MPR UI id request parameter

* Update test

* Update test

* fix: set Vaadin session attribute using lock in reinitializeSession

* Add unit test

* Revert

* Add unit test

Backport to Java 6

* Add imports

* More Java 6

* deprecate vaadin-snapshot (v7)

* update chrome version and screenshot

* update vaadin-bom

Modified cherry-pick of #12385

* fix: Do not allow border to grow row height

If css grows row height the VSrollTable rowHeight logic does not work allways

Fixes: https://github.com/vaadin/framework/issues/12251

* Compensate change in default row height

* Merge branch '7.7' into fix12251

* Replace calc with round

* Make fix more pin-point

* The first row does not have border thus regular height

* Fix drag-drop styles

* Further fix in drag-and-drop style

* Update TableDropIndicatorValoTest-indicator_ANY_Chrome__indicator.png

* Update Jetty version to 9.4.38.v20210224

* Update tests

- Properly init client-side data in GridDataChangeHandlerTest
- Update Chrome version
- Separate and refactor ComboboxMenuBarAutoopenTest test cases to match
test description
- Update screenshot for ResponsiveStylesTest
- Refactor TextAreaEventPropagationTest to better match expected
behavior
- Add delay to GridDetailsClientTest and EscalatorSpacerTest for
stability
- Add delay and retries to TreeItemDoubleClickTest for stability

Co-authored-by: Teemu Suo-Anttila <teemusa@vaadin.com>

Adopted from https://github.com/vaadin/flow/pull/8567

Authored-by: Tatu Lund <tatu@vaadin.com>

Implemented with a listener rather than direct call from UI.detach() in
order to avoid new public API, since the whole feature has been marked
for removal. This doesn't yet prevent the cache or the type map from
getting slightly bloated during the UI's lifetime.

See: #3705

Cherry-picked from: #12199

This hardens the framework against a theoretical timing attack based on
comparing how quickly a request with an invalid CSRF token is rejected.

Backporting of #12188

This is the same as #12190, but also applied for the upload security key
and the push id since both of those are also used to protect against
cross-site attacks. In addition, documentation for the push id is
clarified to point out its role.

Backporting of #12189

Cherry pick https://github.com/vaadin/framework/pull/12131

* Change license from Apache-2 to CVDLv4

* Update header for checkstyle

* Add license checker

* Fix reference header

* Fix license header

* Update Chrome version

- Updated Chrome version
- Added leeway to ComboBox popup following along while scrolling
- Added workarounds to timing issues that aren't relevant for the tests
- Added delays for stability

Fixes: https://github.com/vaadin/framework/issues/7757

There is regression in Vaadin 7.7.16 and later, which is due patch  eafd446726 that can lead to IndexOutOfBoundsException when there is hidden columns while adding new columns, which is similiar issue than earlier reported in https://github.com/vaadin/framework/issues/6784. Essentially the performance improvement patch overwrite some of the fix logic of 8453305743 This fix bring overwriten escalator index compensation back.

ComboBox does not select or add a new value (in case allowed) if User enters the value by typing and TABs out fast. This bug was originally reported in https://github.com/vaadin/framework/issues/4276 and fixed by https://dev.vaadin.com/review/#/c/3564/6/client/src/com/vaadin/client/ui/VFilterSelect.java. However later some logic of VFilterSelect was refactored by patch acb889336f, which accidentally removed the fix. In this new PR I am re-applying the missing part of the logic (adopted to the new structure)

Fixes https://github.com/vaadin/framework/issues/6671

* Updated browsers' screenshots

* Update browsers' screenshots

* Update chrome version to 83

Co-authored-by: Anna Koskinen <Ansku@users.noreply.github.com>

onConnect was allways called with websocket = false. I think this is wrong, since if there was connection loss in websocket, now connection cannot be re-established in websocket mode.

Fixes: https://github.com/vaadin/framework/issues/7190

Cherry pick of https://github.com/vaadin/framework/pull/11884

Co-authored-by: Anna Koskinen <Ansku@users.noreply.github.com>

Fixes #11893

* Change ContextMenu position from absolute to fixed

* Use getBoundingClientRect to get the coordinates of columnSelector in
VScrollTable when the context menu is being opened

* Update TableTooManyColumnsTest screenshot

* Upgrade Chrome version in VerifyBrowserVersionTest

* Update ValoThemeUITest-sliders screenshot

This fixes a compilation error with Eclipse Oxygen.

* Use APPLICATION_SCOPE for the session lock

To be able to do this, relevant methods in VaadinService are made protected so
that VaadinPortletService can override them.

The Vaadin session itself is also stored in APPLICATION_SCOPE. The default
scope is PORTLET_SCOPE, so lock would otherwise not be in sync with
the session.