Add test cases for Tiny containers

Split check-tiny-*-container test case and add some new tests:

• basic functionality
• folder mapping
• device mapping
• AppArmor enforcement
• AppArmot connectivity profile
• custom seccomp policy

Test: https://lava.collabora.co.uk/scheduler/job/1525149 (aa_embedded* were failed since tarball not includes bin.dbus-daemon aa profile yet)

test-cases/tiny-container-system-aa-enforcement.yaml

+metadata:
+  name: tiny-container-system-aa-enforcement
+  format: "Apertis Test Definition 1.0"
+  image-types:
+    tiny-lxc: [ armhf-internal, arm64, amd64 ]
+  image-deployment:
+    - APT
+  type: functional
+  exec-type: automated
+  priority: medium
+  maintainer: "Apertis Project"
+  description: "Test that the AppArmor profile for dbus-daemon is loaded in system-wide
+                privileged container"
+
+  expected:
+    - "Test command should report \"pass\"."
+
+install:
+  git-repos:
+    - url: https://gitlab.apertis.org/infrastructure/tiny-image-recipes.git
+      branch: apertis/v2019dev0
+
+run:
+  steps:
+    - "# Enter test directory:"
+    - cd tiny-image-recipes
+    - "# Setup the AppArmor profile for container:"
+    - sed s/__NAMESPACE_PLACEHOLDER__/lxc-apertis-tiny-system/g lxc/lxc-tiny-connectivity-profile-template | apparmor_parser -qr
+    - "# Check that the AppArmor profile for dbus-daemon in the container is loaded"
+    - lavatests/test-aa-enforcement -a "$ARCH" -r "$RELEASE" -d "$IMAGE_DATE" -t lxc/lxc-tiny-connectivity --aa-namespace "lxc-apertis-tiny-system"
+
+parse:
+  pattern: "(?P<test_case_id>.*-*):\\s+(?P<result>(pass|fail))"