Build up docker images CD workflow

[chensuyue]

Description

Build up docker images CD workflow.

• It supports to manually run build and test with specific images and tags.
• It covers optional jobs with build, scan, test_compose, test_k8s, publish.
• The jobs can be triggered one by one and also can be run together.
• It supports to publish the tested images into public repo with specific tags.

    inputs:
      examples:
        default: "AudioQnA,ChatQnA,CodeGen,CodeTrans,DocSum,FaqGen,SearchQnA,Translation"
        description: 'List of examples to test'
        required: true
        type: string
      tag:
        default: "latest"
        description: "Tag to apply to images"
        required: true
        type: string
      build:
        default: true
        description: 'Build test required images for Examples'
        required: false
        type: boolean
      scan:
        default: true
        description: 'Scan all images with Trivy'
        required: false
        type: boolean
      test_compose:
        default: true
        description: 'Test examples with docker compose'
        required: false
        type: boolean
      test_k8s:
        default: false
        description: 'Test examples with k8s'
        required: false
        type: boolean
      publish:
        default: false
        description: 'Publish Images to docker hub'
        required: false
        type: boolean
      publish_tags:
        default: "latest,v0.9"
        description: 'Tag list apply to publish images'
        required: false
        type: string

TODO:

• Add example related microservice into image build docker compose, so the full build-scan-test-publish workflow for examples could be triggered in one click.
• Add container BoM scan for OSPDT purpose.
• Add test-k8s job.

Issues

This PR is going to accelerate the CD process.

Type of change

List the type of change like below. Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds new functionality)
• Breaking change (fix or feature that would break existing design and interface)
• Others (enhancement, documentation, validation, etc.)

Dependencies

List the newly introduced 3rd party dependency if exists.

Tests

Describe the tests that you ran to verify your changes.

[daisy-ycguo]

lgtm