PrivateTransactionReceipt declares new fields instead of inheriting them

[lyotam]

PrivateTransactionReceipt declares new fields instead of inheriting them

PrivateTransactionReceipt declares again the following fields instead of inheriting them:
private final String contractAddress;
private final String from;
private final String to;
private final List logs;
private final String transactionHash;
private final String status;

This creates two copies of the same field for the superclass (TransactionReceipt) & subclass (PrivateTransactionReceipt), and creates various issues.

Steps To Reproduce

Calling privateTransactionReceipt.isStatusOk()

Expected behavior

Result should be evaluated by the actual receipt status

Actual behavior

Result will always be true because superclass's status is always null, even though subclass status is not.

Environment

Running Besu 1.31 Quickstart network.