[component]: Booking

### Tell us about the new component you’d like to have

As a Workflow Developer,
I want to be able to use the native **Booking** connector,
So that I can implement more complex integration use cases involving **Booking**.

**References**

- Documentation: https://developers.booking.com/connectivity/docs

**Acceptance Criteria**

Implemented actions:

- [ ] [Retrieve inventory and rate details](https://developers.booking.com/connectivity/docs/b_xml-roomrateavailability)
- [ ] [Create or update inventory, rates and restrictions](https://developers.booking.com/connectivity/docs/b_xml-availability)
- [ ] [Create or update derived pricing rates](https://developers.booking.com/connectivity/docs/b_xml-derivedprices)
- [ ] [Retrieving reservations summary](https://developers.booking.com/connectivity/docs/reservations-api/retrieving-reservations-summary)

TODO

Implemented triggers
TODO

Definition of Done:

**Definition of Done**

- [ ] Unit/Integration tests
- [ ] Connection setup steps
- [ ] Guidejar tutorial for connection setup
- [ ] Documentation is generated and available

### Link to the product page

https://www.booking.com/

### Describe the context around this new component

I need a Booking connector to monitor apartment pricing and reservations

### Describe the alternative you are considering or using

so far, no alternative

Start with the linked Booking Connectivity documentation, especially the inventory, availability, derived-prices, and reservations-summary references. Scope discovery must also cover the unspecified triggers and the required connection setup, Guidejar tutorial, generated documentation, and unit/integration tests. Done means the listed actions and triggers are implemented with those tests and supporting materials.

Written by the indexing model from the issue text.