[Ci] Support to build sonic-swss-common

[xumia]

What I did
[Ci] Support to build sonic-swss-common

Why I did it
It is to improve the chance to build successful rate on sonic-swss.
It removes the dependency of the build artifacts of sonic-swss-common in sonic-swss, always uses the latest code of the sonic-swss-common to build it.

How I verified it

Details if related

[vmittal-msft]

@theasianpianist we need this urgently for #2618 to go in. #2618 is needed for pilot testing on chassis.

[theasianpianist]

Why do we want to start building swss-common instead of downloading artifacts?

[vmittal-msft]

Let me copy you on the email thread. sonic-swss compilation is failing due to sonic-swss-common package doesn't seem to be latest enough for this to compile. So why do we have such dependency ? and not directly compile to avoid such issues.

[vmittal-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[xumia]

Why do we want to start building swss-common instead of downloading artifacts?

The build sonic-swss-common is failed in test stage, it blocks the sonic-swss to use the lastest code, and the sonic-swss cannot be built successfully.

[xumia]

Why do we want to start building swss-common instead of downloading artifacts?

The build sonic-swss-common is failed in test stage, it blocks the sonic-swss to use the lastest code, and the sonic-swss cannot be built successfully. It reduces the dependency to wait for the result of another pipeline.

I consider the two aspects as below, any other thoughts? @theasianpianist

1. Is the cost to build the sonic-swss-common low. (5min)
2. Do we want to use the latest sonic-swss-common in sonic-swss?

[vmittal-msft]

As per @prsunny, this need to be included for 202205.
#2648

[prsunny]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[prsunny]

@theasianpianist , merging to unblock PR builds. Lets address any concerns as future commits.