[core] Only one LambdaRuntime.run() can be called at a time (fix #507)

[sebsto]

This is a proposal to fix issue #507

changes

• LambdaRuntime.init() uses a Mutex<Bool> to make sure only one instance is created
• LambdaRuntime.init() can now throw an error in case an instance already exists (I did not use fatalError() to make it easier to test)
• All convenience init() methods catch possible errors instead of re-throwing it to a void breaking the user-facing API
• Renamed existing LambdaRuntimeError to LambdaRuntimeClientError
• Introduced a new type LambdaRuntimeError to represent the double initialization error

[sebsto]

Compiler crashes on nightly build has been reported here
swiftlang/swift#80020

[sebsto]

CI is now green, except API Breakage, which is expected.

[fabianfett]

Great spot! Thanks for tackling this one.

[sebsto]

@fabianfett
I changed

• Mutex for Atomic
• Test is now on run() and not on init()
• LamabdaRuntimeError returned and is now public + one additional error case
• unit test is adjusted and pass

[fabianfett]

some golden rules:

1. we should make sure we never add enums that we want to extend after the release to our public API
2. use structured concurrency when possible

[fabianfett]

you never check if this throws.

[sebsto]

There is a problem in the current code, run() never returns, even when cancelled.

This call blocks

            await #expect(throws: CancellationError.self) {
               _ = try await nonReturningTask.value
            }