Add metrics to track txs reverting

[samlaf]

This morning an avs-sync tx reverted on holesky, but our logs were showing

{"time":"2024-03-28T12:00:14.045938723Z","level":"INFO","source":{"function":"github.com/Layr-Labs/eigensdk-go/chainio/clients/avsregistry.(*AvsRegistryChainWriter).UpdateStakesOfEntireOperatorSetForQuorums","file":"/go/pkg/mod/github.com/!layr-!labs/eigensdk-go@v0.1.3-0.20240318050546-8d038f135826/chainio/clients/avsregistry/writer.go","line":280},"msg":"succesfully updated stakes for entire operator set","tx hash":"0x3537f0bad4f7c7fd8799a24d58ea09a56a8504bd57ff6bb6d8051041402b5b45","quorumNumbers":"[0]"}

This is because I thought txs reverting would result in golang errors, but those only happen when a problem happens with sending the txs. tx reverted was successfully sent to the network, it just reverted while executing its smart contract logic. So to track that, we need to look into the receipt and check the status of the receipt. Added logic to do this.

Also added 3 metrics, that currently look like