Adding CI file

[mohsha-msft]

• The purpose of this PR is explained in this or a referenced issue.
• The PR does not update generated files.
  • These files are managed by the codegen framework at Azure/autorest.go.
• Tests are included and/or updated for code changes.
• Updates to CHANGELOG.md are included.
• MIT license headers are included in each file.

[check-enforcer]

This repository is protected by Check Enforcer. The check-enforcer check-run will not pass until there is at least one more check-run successfully passing. Check Enforcer supports the following comment commands:

• /check-enforcer evaluate; tells Check Enforcer to evaluate this pull request.
• /check-enforcer override; by-pass Check Enforcer (approvals still required).

[benbp]

Azure Pipelines supports "absolute" pathing with template paths that correspond to the repo root. I prefer that approach since it prevents relative pathing issues (which you have here, since you are actually one directory deeper than the ci.yml file I assume this was copied over from).

Suggested change

	- template: ../../eng/pipelines/templates/jobs/archetype-sdk-client.yml
	- template: /eng/pipelines/templates/jobs/archetype-sdk-client.yml

[mohsha-msft]

Ohh I see. I noticed similar changes in https://github.com/Azure/azure-sdk-for-go/blob/main/sdk/azcore/ci.yml where CI is already running so I decided to give it a try. Let me change that and get back to you.

[benbp]

/azp run prepare-pipelines

[azure-pipelines]

No pipelines are associated with this pull request.

[benbp]

We'll need #14947 to go in before we can generate the pipeline for this PR.

[mohsha-msft]

We'll need #14947 to go in before we can generate the pipeline for this PR.

Ohh I see. Great. I can see it has finished working @benbp

[mohsha-msft]

FYI @zezha-msft @nakulkar-msft I'm merging the branch directly