Add a timeout for acquiring dpkg lock. (sonic-net#16328)

What is the motivation for this PR?
In our Impacted Area Based PR testing, we noticed some failure beacuse of the error Could not get lock /var/lib/dpkg/lock-frontend. It is held by process 5166 (dpkg). In this PR, we add a timeout for acquiring dpkg lock to avoid this issue.

How did you do it?
In this PR, we add a timeout for acquiring dpkg lock to avoid this issue.

How did you verify/test it?

.azure-pipelines/impacted_area_testing/calculate-instance-numbers.yml

@@ -11,7 +11,7 @@ steps:
 - script: |
     set -x
 
-    sudo apt-get update && sudo apt-get install -y jq
+    sudo apt-get -o DPkg::Lock::Timeout=600 update && sudo apt-get -o DPkg::Lock::Timeout=600 -y install jq
 
     TEST_SCRIPTS=$(echo '$(TEST_SCRIPTS)' | jq -r -c '."${{ parameters.TOPOLOGY }}"')
 

.azure-pipelines/impacted_area_testing/get-impacted-area.yml

@@ -21,7 +21,7 @@ steps:
     pip install PyYAML
     pip install natsort
 
-    sudo apt-get install -y jq
+    sudo apt-get -o DPkg::Lock::Timeout=600 -y install jq
 
     FINAL_FEATURES=""
     IFS=' ' read -ra FEATURES_LIST <<< "$(DIFF_FOLDERS)"