Switch from calculating transactions' expiration in "number of seconds
since genesis block" to "chain height".

Notice: this change alters the semantic of the maxTransactionAge beyond
just the units (seconds vs height). Before the change we would use the
user-defined transaction.timestamp and add maxTransactionAge (seconds)
to it. After the change we use the current chain height when we have
received the transaction (which is not user-defined and not necessary
the same as when the transaction was created by the user) and add
maxTransactionAge (height) to it.

Resolves #1060

Co-Authored-By: vasild <vd@freebsd.org>

Co-Authored-By: vasild <vd@freebsd.org>

Co-Authored-By: vasild <vd@freebsd.org>

Co-Authored-By: vasild <vd@freebsd.org>

and handle the case if we are unable to get it

The test needs to query the current chain height and then wait until it
increases or fake an increased height.

…tion-expiration-in-height

* ArkEcosystem/core/develop:
  release: 2.3.15 (#2478)
  release: 2.3.14 (#2477)
  refactor(core): remove support for old release channels (#2476)
  fix(crypto): add exceptions for transactions with invalid recipients (#2471)
  refactor(crypto): make all Slots.* methods static (#2473)
  docs(template): add release section to pull request template (#2472)
  chore: fix absolute banner urls (#2469)

…tion-expiration-in-height

* ArkEcosystem/core/develop:
  style: apply linting and formatting to e2e tests (#2480)

…tion-expiration-in-height

* ArkEcosystem/core/develop:
  feat: add core-state to manage the state of in-memory data (#2479)

…tion-expiration-in-height

* ArkEcosystem/core/develop:
  fix(core): parse only the last line of pm2 stdout (#2484)
  release: 2.3.18 (#2488)
  fix(core-snapshots): reset unfinished round after import (#2486)
  fix(core-forger): update configManager height (#2487)
  release: 2.3.16 (#2483)
  fix(core-database): initialize height on startup (#2482)