fix: align log metadata with other SDKs

[zhongkechen]

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Issue Link, if available

Fixes #440

Description

Align durable execution log metadata with the JavaScript and Python SDKs by moving MDC context management into DurableLogger and updating the emitted key names. This also separates logger scope cleanup from durable context objects so context lifecycles are clearer and less error-prone.

• Refactor DurableLogger to manage MDC state through attach/detach helpers instead of storing a logger per durable context.
• Add SafeCloseable so logger context scopes can be used with try-with-resources without checked-exception noise.
• Align MDC field names with the other SDKs by default:
  • executionArn instead of durableExecutionArn
  • root/child durable contexts emit operationId / operationName
  • step contexts continue to emit operationId, operationName, and attempt
• Add LoggerConfig.oldKeyNames to preserve backward compatibility for consumers that still expect the previous MDC field names.
• Remove AutoCloseable / close() responsibilities from durable context types and make logger scoping explicit at user-code execution boundaries.
• Update DurableExecutor, StepOperation, ChildContextOperation, and WaitForConditionOperation to attach/detach logger scope around user code.
• Update ExecutionManager and ParallelDurableFuture to use SafeCloseable instead of AutoCloseable.

Demo/Screenshots

Checklist

• I have filled out every section of the PR template
• I have thoroughly tested this change

Testing

Added a new case testLoggingExample to run logginer-example.

Expanded DurableLoggerTest coverage for:

• replay log suppression behavior
• MDC population for durable and step contexts
• MDC cleanup on detach
• replay-to-execution transition behavior
• all supported log levels
• null request ID handling
• old vs new MDC key expectations

Unit Tests

Yes

Integration Tests

No

Examples

N/A