fix: throw exception when an operation is not declared in ApiResource for parameter attributes on properties

[Maxcastel]

Q	A
Branch?	5.0
Tickets	Related to #7870 & #7899
License	MIT
Doc PR	api-platform/docs#2346

Follow-up of #7870 and #7899.

#[QueryParameter] / #[HeaderParameter] declared on a property can be restricted to a list of operations. Until now, listing an operation that was not declared in #[ApiResource] was silently ignored: the parameter still applied to the declared operations of the list, and the undeclared one had no effect.

#[ApiResource(
    operations: [
        new GetCollection(),
        new Get(),
    ],
)]
class Book
{
    // Before this PR: applied to GetCollection, the Patch was silently ignored
    #[HeaderParameter(key: 'X-Authorization', operations: [new GetCollection(), new Patch()])]
    public string $authToken = '';
}

It now throws a RuntimeException while building the metadata:

Parameter attribute on property "authToken" is restricted to the operation "ApiPlatform\Metadata\Patch" which is not declared on the resource "App\Entity\Book".

[Maxcastel]

Not sure whether it's better to throw an exception when an operation is listed in a parameter but is not declared on the resource, or to silently ignore it. Proposing this approach just in case.

[soyuka]

I like this I'm wondering if we couldn't put this on 5.0 though, wdyt?

[Maxcastel]

Yes, this should have been part of 5.0, as it should have been included in #7899 (it was an oversight). But now that 5.0 has been released, it would cause a BC.

[soyuka]

target 5.0 then :) its a bug fix on our feature

[Maxcastel]

Done @soyuka