feat: add operation to hydra response

[Maxcastel]

Q	A
Branch?	main
Tickets	Closes #2588
License	MIT
Doc PR	api-platform/docs#...

[soyuka]

Mhh we shouldn't do it like this I think. We should keep the default operations, the ones available in a response are there to override or to add new operations capabilities to this resource. See the example at https://www.hydra-cg.com/spec/latest/core/#example-6-a-representation-of-an-issue-augmented-with-a-delete-operation

I'm not sure how users would be able to define this though as I guess that for these to appear the ideal usage would be to have conditions. For example you dont declare the hydra operation globally for DELETE but you choose to show it on the resource for admins.

We'd also need to patch the api-doc-parser to make this work on @api-platform/admin and related tools.

[Maxcastel]

@soyuka

#[HydraOperation] (986443a)
and/or
#[ApiResource(operations: [new Delete(security: "is_granted('ROLE_ADMIN')", hideHydraOperation: true)])] ?

Exemple:

#[ApiResource(operations: [
    new Get(),
    new GetCollection(),
    new Post(),
    new Delete(
        security: "is_granted('ROLE_ADMIN')",
        hideHydraOperation: true,
    ),
])]
#[HydraOperation(
    method: 'DELETE',
    security: "is_granted('ROLE_ADMIN')",
)]

?