Add support to handle additional manual notification providers

[AdmiringWorm]

Checklist

• I have verified this is the correct repository for opening this issue.
• I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.

As part of our releases, we have certain places that needs to be done manually.

Describe The Solution. Why is it needed?

It would be nice to have additional providers added that won't be sending any notifications, but rather would just output the information needed to be posted to the console instead, possibly with information about what needs to be done.

The providers I had in mind for this that isn't implemented would be LinkedIn, Reddit and possibly Facebook (Bluesky as well until it is automated).

This should probably prompt the user to confirm that it has been done before continuing to the next notification provider.

Additional Context

No response

Related Issues

No response

[gep13]

What are your thoughts on this one? Now that we are introducing the --dry-run flag, I think that this one now might be covered? Right?

[AdmiringWorm]

No, it is different.

This is to add support for providers that we can not automate, but we can create local (or output) the notes that should be posted in these location.

For instance, output the necessary notes that should be posted manually on Linkedin, reddit, etc...

[gep13]

But can't we copy/paste the output from running --dry-run=true and then use that as a the basis for the other notifications?

[AdmiringWorm]

If/When those are the same, then yes.

But there are times where these will be different, and you have to figure out manually on what needs to be added/changed. If Cake.Recipe decided that for us, it would make it less likely for an error to made.

This manual notification provider could also include any announcement emails as well (maybe interactively by choosing what to include, not sure).

With everything said though, I do not believe we would include anything in the next release, as there probably are some discussions needed to figure out what to include, how to include it, etc.