Document mutual incompatibility of hx-{delete,get,patch,post,put}

[adamchainz]

These attributes all change the HTTP method. They're presumably incompatible - but what does this do? Does it cause an error, is there a specificity order?

[1cg]

I have no idea what that will do. :/ Well, I imagine it will do all of them, but that's just a guess.

We can update the docs to say so, for sure.

[aburd]

So I did some testing on this and if multiple attributes are specified at the same time, one method will take precedence and only one request is launched, where hx-get has highest priority and hx-patch the lowest.

GET,POST,PUT,PATCH,DELETE => GET
POST,PUT,PATCH,DELETE => POST
PUT,PATCH,DELETE => PUT
PATCH,DELETE => DELETE

I can make a PR with some docs if necessary.

[samfurr]

I believe the order is defined here, where downstream functions eventually parse for the hx elements. @bencroker do we still want this noted in the docs? PR to follow.