Convert renderAdditionalBlockUI to Component and accept props

[getdave]

In #50774 we augmented the renderAdditionalBlockUI render callback. Before this becomes public we should make it accept a Component rather than a function.

This will also solve the issue of a potentially ever expanding list of positional arguments as mentioned in the discussion referenced below.

.......

This now forms part of the API of renderAdditionalBlockUI as positional params. If and when renderAdditionalBlockUI becomes part of the stable API, insertedBlock and setInsertedBlock might not be applicable for some use cases, but we also might want to add additional params at some stage. Would it be worth switching renderAdditionalBlockUI to use an object as its param?

Originally posted by @andrewserong in #50774 (comment)

[Mamaduka]

I started working on this in #51163. I need to do a bit more testing, but PR is ready for early feedback.