update and add examples to new APIs

[tomerd]

motivation: keep code up to date with API changes

changes:

• take advantage of @main where possible
• move the top level Sample code to the examples subdirectory
• extract a few examples form the "LambdaFunctions" directory (which is really a deployment demo) and move them to the top level Examples directory
• rename "LambdaFunctions" examples as "Deployments" to make their intent clearer
• add a sample that demonstrates how to test a lambda now that SwiftPM can test executables directly
• update the test-sample docker setup to build & test th new samples
• fix a few typos and In/Out typealias left overs
• remove LinuxMain since its no longer required

[fabianfett]

What's the benefit of moving the String and Codable sample out of the main Package.swift?

[tomerd]

What's the benefit of moving the String and Codable sample out of the main Package.swift?

its much less noisy. these are really just samples and so they should not be part of the main package. One area where this causes headache is that tools that scan packages (like package collections and package indexes) and cannot tell that these modules are "not important" so they show up as valid modules you may want to use, which his not the intent