[Doc] More Descriptive Budget RPCs

[Liquid369]

Now 'getbudgetprojection' for isEstablished is more defined.
As well as 'getbudgetinfo' is a little more descriptive.
As per the request in discord just browsed the file for some areas where I think the information could be used.

[furszy]

As getbudgetprojection return only proposals that are passing for the next superblock, the returned values IsEstablished, IsValid and IsInvalidReason are redundant and can be removed, all of them will always be true / not used for every returned item.

Better to modify the base description of getbudgetprojection, adding the requirements for a proposal to be on the returned list. Example of two main requirements that could cause confusion if aren't stated somewhere:

Show the projection of which proposals will be paid the next cycle.
* Proposal fee tx time need to be +24hs old from the current time.
* The net votes value need to be higher than the masternodes count divided by ten.

[random-zebra]

As getbudgetprojection return only proposals that are passing for the next superblock, the returned values IsEstablished, IsValid and IsInvalidReason are redundant and can be removed

These fields are filled in budgetToJSON, which is used also by getbudgetinfo where they are not redundant.

[Liquid369]

Modifications made and pushed/squashed commits
@random-zebra dangit timing haha

[furszy]

These fields are filled in budgetToJSON, which is used also by getbudgetinfo where they are not redundant.

@random-zebra, i said that are redundant for getbudgetprojection, not for getbudgetinfo.

[Liquid369]

Updated

[random-zebra]

Looks good to me. utACK bc50042

[furszy]

utACK be59d5c

[random-zebra]

utACK be59d5c and merging...