Improve debuggability of exported method numbers.

[Stebalien]

For example, there's no easy way to figure out what method 2280458852 on the market actor is.

[Abhay-2811]

Hey @Stebalien is it ok if I start working on this?

[Stebalien]

Sure! If you have an idea of how to solve it. The only thing I can think of is to auto-generate documentation.

[Abhay-2811]

Can you elaborate on the issue I'm new to the repo and trying to understand the code base. If you have any insights that might help!

[Stebalien]

Basically, "exported" methods are assigned method numbers according to FIP-0042. Unfortunately, that means that, if someone sees a message with the method number 3302309124, they're going to have a lot off difficulty figuring out which method that is. In this case, the method is ChangeWorkerAddress on the Miner actor.

The goal of this issue is to provide some form of auto-generated documentation that maps these method numbers back to their method names. Probably by auto-generating some form of json document that can then be imported into the main Filecoin documentation.

However, this is a pretty open-ended project, isn't very well defined, and is probably not very approachable for newcomers. I'm not sure why it was tagged as a good first issue, but I've removed that label.