Add information on current bias holder for BiasedLockRevocation event

When a biased lock revocation event is issued, it would be nice to include information on which thread was currently holding the bias.

The thread pointer is present in the mark word, but needs to either be validated when the event is generated (possibly using thread SMR for efficiency), or extracted during the actual revocation operation and passed to the event generation through the VM operation struct.