feat(release-please)!: consolidate manifest and individual releasers

[bcoe]

Major update to release-please which consolidates the manifest and single
releaser behavior into a single set of strategies, which can be used
on both split and mono-repos.

feat: adds support for draft pull requests.
feat: adds support for draft releases.
refactor!: if switching to manifest releaser, release_created will only be set if "." path is published.
refactor!: switch to using @actions/core getBooleanInput, accepted values for true = ["true", "True", "TRUE"], accepted values for false = ["false", "False", "FALSE"].

[kalosisz]

hey @bcoe, I believe this would allow to create draft PR, but not draft Github releases. Am I wrong?

[live627]

Can you add documentation for upgrading?

[kalosisz]

Could you please allow this args to set? Thanks

https://github.com/googleapis/release-please/blob/28bc76b35d9e1eff218a5be1b9b8cebb4b1e6f9d/src/bin/release-please.ts#L189-L196

[bcoe]

Could you please allow this args to set? Thanks

@kalosisz sure thing.

Can you add documentation for upgrading?

I don't believe there will ultimately be any major changes that need to be made to upgrade. There is some underlying behavior that changes, such as the branch naming convention, which does make this a breaking change (but shouldn't affect most people).

[goatwu1993]

@bcoe maybe it is a good time to bump action/core to the latest version(1.6.0)？ （since this is a major release?）

Release note: https://github.com/actions/toolkit/blob/main/packages/core/RELEASES.md

1.3.0 @action/core introduced getBooleanInput. Since core.getBooleanInput accepts fewer strings, it is a BREAKING change. Good timing to remove housemadegetBooleanInput and use core.getBooleanInput (if you like to). String accepted can be found here

1.4.0 @action/core introduced getMultilineInput which returns string[], which googleapis/release-please#1157 may take advantage of.

[chingor13]

1.3.0 @action/core introduced getBooleanInput. Since core.getBooleanInput accepts fewer strings, it is a BREAKING change. Good timing to remove housemadegetBooleanInput and use core.getBooleanInput (if you like to). String accepted can be found here

Switching the boolean helper sounds like a good change to make before releasing v3 of the action. Perhaps in a follow-up PR before the new tag?

1.4.0 @action/core introduced getMultilineInput which returns string[], which googleapis/release-please#1157 may take advantage of.

We can use this without a breaking change when surfacing new options