Adopted 1es common template

[raych1]

• Adopted the 1es pipeline template
• Published all the artifacts and logs to the pipeline artifacts
• Moved this pipeline yml file to stages folder

[raych1]

It would be good to suppress these warnings or ignoring the steps since this pipeline is mainly to generate SDK code. @benbp, do you have any idea how to do that if we should do it?

Here is a sample run

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[benbp]

@raych1 the github related ones should go away soon as they are addressing that issue. For the others, either the underlying issues can be fixed (component governance), or we can add skips to the top level 1es config. We haven't been able to eliminate every warning, as each one takes its own investigation.

[raych1]

@raych1 the github related ones should go away soon as they are addressing that issue. For the others, either the underlying issues can be fixed (component governance), or we can add skips to the top level 1es config. We haven't been able to eliminate every warning, as each one takes its own investigation.

I don't see any special configuration needs to make for spec repo since this pipeline is bound to the spec repo except this change. Do you have any concern?