For the /v1/embed-yourself api some of the forwarding's are missing in the specification

[ManasaBM1]

Issue Description: As per latest Specification of the MWDI 2.1.2 , Some of the necessary forwarding's which is required for the Embedding Process are missing.

The below forwarding's are important to embedding process and they are missing in the Specification:

• PromptForEmbeddingCausesCyclicLoadingOfDeviceListFromController
• PromptForEmbeddingCausesCyclicLoadingOfDeviceListFromCache
• PromptForEmbeddingCausesSelfCallingForLoadingOfControlConstructForDevicesNotInCache
• PromptForEmbeddingCausesDeletingUnconnectedDevicesFromCache
• PromptForEmbeddingCausesSubscribingForNotifications

But this forwarding information mentioned in the MicroWaveDeviceInventory+forwardings.yaml file

[IswaryaaS]

Apart from above mentioned callbacks, below callbacks shall also be added as per forwardings file:

• PromptForEmbeddingCausesUpdatingMetadataTableInElasticSearchFromDeviceListSync
• PromptForEmbeddingCausesCyclicLoadingOfDeviceStatusFromController
• PromptForEmbeddingCausesCyclicLoadingOfDeviceStatusMetadataFromElasticSearch
• PromptForEmbeddingCausesUpdatingDeviceStatusMetadataInElasticSearch

[kmohr-soprasteria]

i.e. in total we have the following missing forwardings:

• 1: PromptForEmbeddingCausesCyclicLoadingOfDeviceListFromController
• 2: PromptForEmbeddingCausesCyclicLoadingOfDeviceListFromCache
• 3: PromptForEmbeddingCausesSelfCallingForLoadingOfControlConstructForDevicesNotInCache
• 4: PromptForEmbeddingCausesDeletingUnconnectedDevicesFromCache
• 5: PromptForEmbeddingCausesSubscribingForNotifications
• 6: PromptForEmbeddingCausesUpdatingMetadataTableInElasticSearchFromDeviceListSync
• 7: PromptForEmbeddingCausesCyclicLoadingOfDeviceStatusFromController
• 8: PromptForEmbeddingCausesCyclicLoadingOfDeviceStatusMetadataFromElasticSearch
• 9: PromptForEmbeddingCausesUpdatingDeviceStatusMetadataInElasticSearch

Those targeting ElasticSearch need to be handled individually:

• (A) access to ElasticSearch related to ressource paths: paths are specified explicitly in the forwardings; the callback needs also to be included in the OAS
• (b) access to ElasticSearch NOT related to ressource paths: in the forwardings only ElasticSearch in general is given; the callbacks are NOT to be included in the OAS

Changes:

• The following forwardings targeting ElasticSearch will only be included in the forwardingList, but not as callbacks in the OAS: 4, 6, 8, 9
• to be added in OAS: 1, 2, 3, 5, 7

[kmohr-soprasteria]

Callback 5 (PromptForEmbeddingCausesSubscribingForNotifications) has 5 consequent requests, these will be added under 1 callback with 5 substeps

[kmohr-soprasteria]

fixed by #1111