Value Statement

Ensure the issue title clearly reflects the value of this user story to the
intended persona. (Explain the "WHY")

The ansible integration in Appsub model got performance issues when verified in large scale test env.  Two issues are reported 

https://issues.redhat.com/browse/ACM-8538

https://issues.redhat.com/browse/ACM-8636

Both are caused by the same reason - a lot of more unnecessary ansible jobs are created due to placement decision reconciliation.  This could happen easily when a placement is to select thousands of clusters and it could take a while to make the final placement decision list ready. During this period, every placecement decision change triggers one ansible job creation. 

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [X] Unit/function tests have been automated and incorporated into the
  build.
• [X] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [X] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [X] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [X] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [X] The must-gather script has been updated.