Avoid configuration not updated after reasonable configuration changes

Considering the sequence has wrapped around if the sequence number has
a significant large jump. Obviously the original value (0x10000) is not
big enough nowadays.

Also taking the negative jump into account, where the wrap around may
happen on the `other` configuration.

Bug: 239371596
Test: ConfigurationTest
Change-Id: I8ac5ee8c1589b68e63e8e29f961c7fcba719949e