[DO NOT MERGE] fix: ensure configured package manager is used

[agdimech]

Issue

N/A

Description

The Projen blueprint assumes yarn is used. If a user specifies an alternative package manager, yarn is still used.

Testing

Untested

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[agdimech]

@alexforsyth - is projen-blueprint-component still used?

[alexforsyth]

@agdimech it should be used? What do you mean?

I believe that component is the projen construct behind all of the packages/components/

[agdimech]

@agdimech it should be used? What do you mean?

I believe that component is the projen construct behind all of the packages/components/

It looks like alot of the code is duplicated with https://github.com/aws/codecatalyst-blueprints/blob/main/packages/utils/projen-blueprint/src/blueprint.ts. Perhaps we should refactor into common code?

[alexforsyth]

The code between
(backs the blueprint codebase construct itself)
https://github.com/aws/codecatalyst-blueprints/blob/main/packages/utils/projen-blueprint/src/blueprint.ts

and
(backs the blueprint component codebase construct itself)
https://github.com/aws/codecatalyst-blueprints/blob/main/packages/utils/projen-blueprint-component/src/blueprint.ts

Is similar but its not exactly the same. You'll notice that components have a series of different commands they use to build themselves. For example, most of the blueprint publishing, etc, commands dont make sense for the components. The components are essentially minor upgrades across the typescript component.

See example usage here in the source repo component
https://github.com/aws/codecatalyst-blueprints/blob/main/packages/components/source-repositories/.projenrc.ts#L1