[0yi0]

Summary

As described in WasmEdge#4277, move WasmEdge image definitions and their build workflows into WasmEdge/devcontainer so they can be maintained independently.

• Import the Docker image definitions and dependency-family scripts, .dockerignore, and the image, Alpine/Debian static, and OpenWrt workflows from WasmEdge 0.18.1 at b2e483553ea7a1826be117180125c71e5d0b8958.
• Keep Dockerfile.*, docker-bake.*.hcl, SHA256SUM.*, and build-manylinux.sh at repository root, with Dockerfile-consumed dependency inputs under scripts/<family>/.
• Keep the import commits faithful to the identified snapshot; required destination adaptations follow in separate commits, not under upstream authors' provenance.
• Use the consolidated .github/workflows/docker.yml for image validation and publication.
• Configure .devcontainer for developing WasmEdge/devcontainer, using wasmedge/wasmedge:ci-image-base and the name WasmEdge devcontainer development.

Commit organization and required adaptations

1. feat(docker): import WasmEdge image definitions and dependencies — faithful image-definition, dependency, and build-input import. Relocate the source Docker and dependency paths into the destination layout while preserving source whitespace, executable modes, target groups, and image behavior.
2. ci(docker): import WasmEdge image and platform workflows — faithful import of the Docker, Alpine static, Debian static, and OpenWrt workflows. Preserve their triggers, job dependencies, containers, matrices, Docker Hub login/push conditions, and conditional release uploads.
3. ci(docker): provide release sources for standalone builds — download the WasmEdge 0.18.1 archive for static and OpenWrt workflows, provide the static source context and version marker, supply the OpenWrt source and package Makefile, and remove the unavailable C++ reusable-linter job.
4. ci(docker): adapt imported workflows to this repository — use main for the push trigger and remove the obsolete split Ubuntu and manylinux workflows, leaving docker.yml as the consolidated image workflow.
5. chore(devcontainer): configure repository development environment — configure the repository devcontainer to use wasmedge/wasmedge:ci-image-base.
6. docs: document repository layout — document the repository layout.
7. fix(ci): resolve ShellCheck findings in workflow scripts — resolve SC2046, SC2086, and SC2129 in the affected workflows.

Import commit messages identify the exact source snapshot and retain source PR/direct-commit references and original author information. Those references describe imported content, not the later destination adaptations.

Publishing

• Pull-request runs build the images without pushing them. Non-PR runs retain the imported Docker Hub login and image-push behavior.
• The static reusable workflows upload release assets only when called with release: true; the OpenWrt workflow is manual and is not part of the pull-request checks.
• GHCR publishing and ownership changes are outside this PR.

Verification limits

• The OpenWrt workflow is triggered manually and is not covered by the pull-request checks.
• Pull-request checks do not push images to Docker Hub or upload release assets, so those publication paths are not validated here.