Missing type field in transaction objects

[JosephK95]

Description

According to the Ethereum API specification, type field in transaction object is mandatory. However, it seems that Besu does not have the field when returning a transaction object.
(Specification link: https://github.com/ethereum/execution-apis)

Expected behavior:
Besu should return a transaction object of the following form:

{
  ...
  value: '0',
  type: 0,
  v: '0x42',
  r: '0xe60a9bbb92a74e167c3b49900891dc181d6568ee473b923ba7b752a6025b011b',
  s: '0x594dc4b227cb453b697c67a175b50f1ac4ea4578dba2f91abed8b863bbff62d3'
}

Actual behavior:
Besu returns a transaction object without type field:

{
  ...
  value: '0',
  v: '0x42',
  r: '0xe60a9bbb92a74e167c3b49900891dc181d6568ee473b923ba7b752a6025b011b',
  s: '0x594dc4b227cb453b697c67a175b50f1ac4ea4578dba2f91abed8b863bbff62d3'
}

Frequency:
Always

Versions (Add all that apply)

• Software version: besu/v22.4.4/linux-x86_64/openjdk-java-16
• OS Name & Version: Ubuntu 20.04.4 LTS