Add PD status to the debug menu

[Ralim]

This is a todo item im spinning out of #734.

Want to add some more metrics to the debug menu to indicate:

• FUSB present
• What state it is in

[Civil]

So far I've for myself implemented simple debug menu which just prints out Status register statuses during initialization at various points (as dec10 values) and all status (status0, status1, status0a, status1a; currently I can't see how interrupt registers might be useful) on a screen which was helpful enough for me to look through datasheet and confirm that it's likely CC1 is in the air on my device (though I'm waiting for a replacement Pinecil, so I don't have a fully working device yet). Oh, and I obviosuly haven't tried it on ts100 as I don't have one. But I kept wondering why fusb302 driver was implemented twice (for ts100 and pinecil), even though they seems to be 99% identical (except for extra locks in ts100 driver, which could've been just Noop on Pinecil if they are not needed)

If you are interested in something like that, I can create a PR (or modify debug menu to include information in some more readable state)

[Ralim]

Not sure how I missed this. Would be open to any ideas on how best to indicate the extra information :)

[Civil]

M... I no longer remember what was the description of status registers in datasheet, but even raw dump + datasheet was already helpful for me to confirm that it was a hw failure.

So I guess it would be great to have human readable description of status registers of fusb302