fix(aws-codebuild): rename the Project methods for adding Actions to CodePipeline

[skinny85]

BREAKING CHANGE: this renames the public methods of the Project class,
addBuildToPipeline and addTestToPipeline, to addToPipeline and
addToPipelineAsTest, respectively.

Fixes #1211

---

Pull Request Checklist

Please check all boxes (including N/A items)

Testing

• Unit test and/or integration test added
• Toolkit change?: integration
  tests
  manually executed (paste output to the PR description)
• Init template change?: coordinated update of integration tests
  (currently maintained in a private repo).

Documentation

• README: README and/or documentation topic updated
• jsdocs: All public APIs documented

Title and description

• Change type: Title is prefixed with change type:
  • fix(module): <title> bug fix (patch)
  • feat(module): <title> feature/capability (minor)
  • chore(module): <title> won't appear in changelog
  • build(module): <title> won't appear in changelog
• Title format: Title uses lower case and doesn't end with a period
• Breaking change?: Last paragraph of description is: BREAKING CHANGE: <describe exactly what changed and how to achieve similar behavior + link to documentation/gist/issue if more details are required>
• References: Indicate issues fixed via: Fixes #xxx or Closes #xxx

---

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

[eladb]

LGTM.

The phrasing of the "BREAKING CHANGE" paragraph should be read as "what concrete information a user that reads the changelog needs to know". For example:

BREAKING CHANGE: `addBuildToPipeline` was renamed to `addToPipeline` 
and `addTestToPipeline` was renamed to `addPipelineToTest` in order to align 
with naming conventions.

Something like that.

[skinny85]

LGTM.

The phrasing of the "BREAKING CHANGE" paragraph should be read as "what concrete information a user that reads the changelog needs to know". For example:

BREAKING CHANGE: addBuildToPipeline was renamed to addToPipeline
and addTestToPipeline was renamed to addPipelineToTest in order to align
with naming conventions.

Something like that.

Sure. Changed when merge squashing the commit.