Server guide packaging

[heckj]

Summary

Updates and migrates content from swift.org article into DocC, expanding two two articles - one focused on building containers for your service, and another touching on using the Static Linux SDK for direct binary generation.

Related Issue

Closes: #17

Type of Change

• Content error fix (corrects inaccurate information)
• Enhancement (improves existing content)
• New content (adds new documentation)
• Technical change (build system, tooling, infrastructure)
• Typo or formatting fix

Documentation Package(s) Affected

• API Guidelines
• Language Guides
• Server Guides
• Ecosystem Tools
• Repository infrastructure

Testing

Build Verification

• Ran swift package generate-documentation --analyze --warnings-as-errors successfully
• Previewed documentation locally with swift package --disable-sandbox preview-documentation

Content Review

• Changes follow the Apple Style Guide
• Changes follow TSPL style guidelines
• Code examples compile and run as expected
• Links and cross-references are valid

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

[0xTim]

So overall this tutorial looks great but I'm not sure we want to make this server specific? CLI tools especially work great with the static SDK

[heckj]

I see where you're going, however I'm not sure how we'd broadly like to reconcile initial goals of porting and updating the swift server guides into DocC and getting them published, specific to the server side use cases. I totally agree it's a fantastic possible mechanism to make easily-used executables that can run on linux or macOS (or other platforms, as long as they can run a Linux container).

I've got queued up to move the "getting started with Static Linux SDK" as it's own article - and it sounds like "Swift on Linux" is a worthwhile thing, @FranzBusch has made the same comments to me. So let me ask - does this article sound like it's wrong or doesn't fit here, because it's more aligned elsewhere or with something else, or are you thinking that we just need a broader scope for content that is "Swift on Linux" more generally?

[FranzBusch]

In my opinion, general guides for building Swift applications and another guide for building docker images makes sense. Neither of those should be tied to the Swift Server use-case since they are generally useful to many different use-cases.