eDiscovery Operation return values should include data from Location header

[hinchliff]

Describe the bug

Some of the eDiscovery APIs return the Operation information in the Location header, but the SDK is not returning this information.

this makes it nearly impossible to track the status of the Operation, because you don't know which operation to track.

• https://learn.microsoft.com/en-us/graph/api/security-ediscoverysearch-estimatestatistics?view=graph-rest-1.0&tabs=http
• https://learn.microsoft.com/en-us/graph/api/security-ediscoverysearch-exportresult?view=graph-rest-1.0&tabs=python

the code should be updated to at minimum return the Location header info, or ideally to simply return the Operation ID.

Expected behavior

The SDK endpoints that create an eDiscovery operation should return the operation id.

How to reproduce

Follow the code snippets in the docs:

# Code snippets are only available for the latest version. Current version is 1.x
from msgraph import GraphServiceClient
from msgraph.generated.security.cases.ediscoverycases.item.searches.item.microsoft_graph_security_export_result.export_result_post_request_body import ExportResultPostRequestBody
from msgraph.generated.models.export_criteria import ExportCriteria
from msgraph.generated.models.additional_options import AdditionalOptions
from msgraph.generated.models.export_format import ExportFormat
# To initialize your graph_client, see https://learn.microsoft.com/en-us/graph/sdks/create-client?from=snippets&tabs=python
request_body = ExportResultPostRequestBody(
	display_name = "Export 1 - simple PST",
	export_criteria = ExportCriteria.SearchHits,
	additional_options = AdditionalOptions.HtmlTranscripts | AdditionalOptions.SplitSource | AdditionalOptions.IncludeFolderAndPath | AdditionalOptions.CondensePaths | AdditionalOptions.FriendlyName,
	export_format = ExportFormat.Pst,
)

await graph_client.security.cases.ediscovery_cases.by_ediscovery_case_id('ediscoveryCase-id').searches.by_ediscovery_search_id('ediscoverySearch-id').microsoft_graph_security_export_result.post(request_body)

(although most of them are broken)

SDK Version

1.45.0

Latest version known to work for scenario above?

No response

Known Workarounds

No response

Debug output

Click to expand log

```

</details>


### Configuration

_No response_

### Other information

_No response_