docs: Remove 'queue' parameter requirement from event stream document…

[Egor-OSSRevival]

Fix: Remove queue parameter requirement from event stream documentation
This commit addresses the discrepancy between the Event Stream API's behavior and its documentation regarding the queue parameter.

The queue parameter was previously documented as a required, unique identifier for clients sharing the same event types and filter. However, the underlying code only checked for its presence without implementing any of the documented logic, as this was removed in a prior change (#7088).

To resolve this, the following changes have been made:

lib/remote/eventshandler.cpp: The check requiring the presence of the queue parameter has been removed.

doc/12-icinga2-api.md: The documentation has been updated to remove the queue parameter from the list of required parameters for the event stream.

[cla-bot]

Thank you for your pull request. Before we can look at it, you'll need to sign a Contributor License Agreement (CLA).

Please follow instructions at https://icinga.com/company/contributor-agreement to sign the CLA.

After that, please reply here with a comment and we'll verify.

Contributors that have not signed yet: @Egor-OSSRevival

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Please contact us if you think this is the case.

• If you signed the CLA as a corporation, your GitHub username may not have been submitted to us. Please reach out to the responsible person in your organization.

[Egor-OSSRevival]

Signed

[oxzi]

@cla-bot check

[cla-bot]

Thank you for your pull request. Before we can look at it, you'll need to sign a Contributor License Agreement (CLA).

Please follow instructions at https://icinga.com/company/contributor-agreement to sign the CLA.

After that, please reply here with a comment and we'll verify.

Contributors that have not signed yet: @Egor-OSSRevival

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Please contact us if you think this is the case.

• If you signed the CLA as a corporation, your GitHub username may not have been submitted to us. Please reach out to the responsible person in your organization.

[Egor-OSSRevival]

@cla-bot check

[cla-bot]

Thank you for your pull request. Before we can look at it, you'll need to sign a Contributor License Agreement (CLA).

Please follow instructions at https://icinga.com/company/contributor-agreement to sign the CLA.

After that, please reply here with a comment and we'll verify.

Contributors that have not signed yet: @Egor-OSSRevival

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Please contact us if you think this is the case.

• If you signed the CLA as a corporation, your GitHub username may not have been submitted to us. Please reach out to the responsible person in your organization.

[oxzi]

Thanks for creating this PR.

The change looks good so far and API requests sill sending the queue parameter should still work.

Someone else should take a look at the CLA bot thingy.

[Egor-OSSRevival]

Thank you, I have signed for two times now(one yesterday and one today) and still got this message

[bobapple]

@cla-bot check

GHA failed

[Al2Klimov]

Please could you keep the file sorted alphabetically?