Request: Add complete documentation for transforms

[GuybrushX]

The following deploy was an undelegation:
https://cspr.live/deploy/786ee3fea3ece2d9914c8556bd7948c3a1962a84dd8b9d336f3180b300847e89

But it is very hard to detect because according to an CL engineer at Discord this is the solution:

Browsing the transform we can see this indicating it is a undelegation.

{
  "key": "withdraw-e386a6e2d67ab4c7af524f0b7f60fa77fe420a189309b613f359ccd83c27807a",
  "transform": {
    "WriteWithdraw": [
      {
        "amount": "187844144814190",
        "bonding_purse": "uref-ef79f1606502ae33d549a4ca7233bfcca216fa1f1bb2f06448dc6c5aef03cad2-007",
        "era_of_creation": 10000,
        "unbonder_public_key": "0147d2fd67373271b125985d8911f37d431a26a571326cf297156c3cae9fdab85f",
        "validator_public_key": "01000e6fce753895c0d08d5d6af62db4e9b0d070f10e69e2c6badf977b29bbeeee"
      }
    ]
  }
}

So according to my understanding you can call system contracts and their entrypoints from your own smart contract. If someone wants or needs to track them (for any kind of analysis, statistics, notifications etc.) currently this can be achieved only by reverse engineering and lots of try & error and it always has the potential to fail because of other undocumented ways of doing the same thing in different ways.

I also heard from other developers that parsing transforms is a big challenge because so many things aren't publicly documented.