fix(aws-codepipeline): update cfn example

[AllanZhengYP]

This test is referred as example in the Cloudformation README. But the example doesn't do what it intended. Without specify the runOrder the pipelineExecuteChangeSetAction will be triggered immediately without change set being populated, which will lead to deployment failure. After adding the runOrder the 3 actions will run in order and only be deployed after manual aproval

---

Pull Request Checklist

• Testing
  • Unit test added
  • CLI change?: coordinate update of integration tests with team
  • cdk-init template change?: coordinated update of integration tests with team
• Docs
  • jsdocs: All public APIs documented
  • README: README and/or documentation topic updated
• Title and Description
  • Change type: title prefixed with fix, feat will appear in changelog
  • Title: use lower-case and doesn't end with a period
  • Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
  • Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"
• Sensitive Modules (requires 2 PR approvers)
  • IAM Policy Document (in @aws-cdk/aws-iam)
  • EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
  • Grant APIs (only if not based on official documentation with a reference)

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.

[AllanZhengYP]

Can anyone help me with the CI?

[eladb]

@skinny85 can you take a look please?

[skinny85]

Thanks for the contribution @AllanFly120 . Since this file is part of our integ tests, you also need to update its corresponding expectations file, integ.cfn-template-from-repo.lit.expected.json. You can do it by running npm run integ -- integ.cfn-template-from-repo.lit.js in the aws-codepipeline package, which will deploy, and then remove, the test Stack into your AWS account, and write out the contents of the expectation file. More info on our integ tests is here.

[skinny85]

I updated the expected JSON file.