Carry over sticky activation for same-origin navs and traversals

See discussion in https://github.com/WICG/view-transitions/issues/239
and https://github.com/whatwg/html/issues/11328#issuecomment-2937353307.

Details:

- To avoid encouraging racy code, this is sticky activation only, not
  transient activation. This requires adding the "has sticky activation"
  boolean to the user activation data model.
- This does not propagate the information to iframes or parent frames.
  It is only for the navigated frame (which can be an iframe), and it
  copies from its predecessor Window in that same frame.
- This works for push/replace navigations, reloads, and both bfcached
  and non-bfcached traversals, except for iframes recreated during
  non-bfcache traversals.
- Reloads reuse the entry's document state, which describes the original
  navigation, so they only check whether the reload itself was redirected
  cross-origin.
- Unless reloading, the destination entry must have a same-origin
  initiator origin (excluding navigations initiated by a cross-origin
  document or browser UI) and must not have been created via
  cross-origin redirects. To make the latter hold after bfcache
  eviction, a "was created via cross-origin redirects" bit is added to
  document state.
- history-action user activation is redefined as a simple boolean
  instead of comparing timestamps, fixing a bug where consuming
  transient activation re-granted history-action activation without a
  new user gesture.

Co-authored-by: Philip Jägenstedt <philip@foolip.org>