Support scopes with Amazon.Lambda.Logging.AspNetCore JSON logger

### Describe the feature

It was briefly discussed in this PR:
https://github.com/aws/aws-lambda-dotnet/pull/2083#issuecomment-3046312828

Therefore, adding a separate feature request here.

Currently AspNetCore JSON logger does not support logging scopes. It would be really nice if it did.

It was also requested for non-AspNetCore scenarios:
https://github.com/aws/aws-lambda-dotnet/issues/1747#issuecomment-2450860295

### Use Case

Scopes are heavily used with Otel, so currently we lose tracing information.
Apart from that, we heavily use custom scopes, like tenantId, userId, etc.

### Acknowledgements

- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### AWS .NET SDK and/or Package version used

Amazon.Lambda.Logging.AspNetCore 4.1.0

### Targeted .NET Platform

.NET 8

### Operating System and version

AmazonLinux

Beginnen Sie damit, den JSON-Logger von Amazon.Lambda.Logging.AspNetCore zu lokalisieren und die Diskussion in PR 2083 und Issue 1747 zu prüfen. Ermitteln Sie, wie Logging-Scopes dargestellt werden und welche bestehenden Tests dies abdecken, und definieren Sie anschließend die Fertigstellung so, dass OpenTelemetry- und benutzerdefinierte Scope-Informationen in JSON-Logs erhalten bleiben, ohne das aktuelle Logger-Verhalten zu verändern.

Vom Indexierungsmodell aus dem Issue-Text verfasst.