common: update status fields for EIPs and hardforks

[ryanio]

Closes #1773

Have only updated the "status" fields, the rest are prettier formats.

(I wonder if we should open a separate PR to format all of our JSON and markdown files in the monorepo at once, the command from root would be: npx prettier "**/*.{json,md}" --write)

[codecov]

Codecov Report

Merging #1777 (6288c49) into master (ba916e5) will not change coverage.
The diff coverage is n/a.

Flag	Coverage Δ
block	85.57% <ø> (ø)
blockchain	83.28% <ø> (ø)
client	75.82% <ø> (ø)
common	93.90% <ø> (ø)
devp2p	82.56% <ø> (ø)
ethash	90.76% <ø> (ø)
trie	80.02% <ø> (ø)
tx	88.20% <ø> (ø)
util	92.62% <ø> (ø)
vm	81.17% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[holgerd77]

Ah, no, this status here is really the EIP status. This EXPERIMENTAL is only used in the VM to then indicate the status of the implementation.

I guess if we update here to EXPERIMENTAL and mix this with the EIP states it get's chaotic. That said, this status field is also only used internally, I added this when setting up the Common class with the above semantics in mind. Not sure if it's very helpful and we generally want to keep or not.

We might want to discuss separately. In doubt we just repeat redundant information here, which will likely always get outdated again and again. I guess if we decide we could even "just remove" without the fear of any breaking-change consequences.

Nevertheless: for now will update here back to Draft to keep things consistent.

[holgerd77]

But, to add some own opinion on that: I am currently also undecided (to remove or not), this might also be some useful helper on the status of EIPs we have implemented (otherwise one would likely not always look this up manually).

[holgerd77]

LGTM

[jochem-brouwer]

Great, thanks! But moving 2315 to experimental in VM has not been addressed here (have reopened the issue).