Implement Batch processing when creating IRS jobs

**As** Trace-X
**I want**to use the /irs/order endpoint instead of synchronizing each asset separately
**so that** to improve the way of synchronizing assets using irs

## Link
- child of https://github.com/eclipse-tractusx/sig-release/issues/219
- duplicates https://github.com/eclipse-tractusx/traceability-foss/issues/418

## Hints / Details
- IRS is providing endpoints to create batch jobs.
https://irs.int.demo.catena-x.net/api/swagger-ui/index.html?configUrl=/api/api-docs/swagger-#/Item%20Relationship%20Service/registerOrder

- currently we are creating single jobs and handling callbacks accordingly.
we could create single batch for synchronizing assets . or even consider creating batch per asset for upward and downward asset resolution. that could be later on used to display for user which assets are currently in process of synchronizing data.
- Align on the required batchStrategy for irs required by Trace-X

## Acceptance Criteria
- [ ] Backend is creating batch job/jobs for clear and simplified synchronization logic

Start by reviewing the IRS registerOrder API documentation and the current single-job and callback handling described in the issue. Check the linked duplicate issue and align the required batchStrategy before defining the batch job behavior. Done means the backend creates batch job(s) with simplified synchronization logic and satisfies the acceptance criterion.

Written by the indexing model from the issue text.