Make patch type required

[negz]

See discussion at #16 (comment).

This would almost certainly make porting to function-patch-and-transform more of a pain for most folks, but it may be worth it to make P&T Compositions more explicit and readable in future.

[ytsarev]

In this case, the migration from the current Crosslane core P&T will be more than just indenting the yaml :)
I believe it's ok, just needs to be documented somewhere explicitly.

[stevendborrelli]

This could be added to https://github.com/crossplane-contrib/crossplane-migrator in the same we we populate missing ConnectionSecret keys.

[stevendborrelli]

Added issue here crossplane-contrib/crossplane-migrator#6

[stevendborrelli]

I've merged the fix to the migrator:

• the migrator will add missing transform types
• if the patch type is not specified it will add the default type
• it will generate a name for the resource if not specified

[negz]

I'm kind of feeling like the ship has sailed on this one. There's enough folks using this function now that we probably can't make such a breaking change easily. I feel okay leaving it as is - let me know if anyone disagrees.