feat: add support for formatting code from stdin

[calebdw]

Hello!

Resolves #262, resolves #162

There's tools and editors (e.g., zed, https://jj-vcs.github.io/jj/latest/cli-reference/#jj-fix) that can integrate with formatters if the formatter accepts input on stdin and outputs the changes on stdout. This PR adds that functionality to pint

CC: @TheBlckbird, @bilogic, @serbanrobu, @gabrielbidula

Thanks!

[calebdw]

Thank you sir!

[saade]

This PR somehow breaks the Laravel Pint as well the official Laravel VSCode extensions.

For context:
open-southeners/vscode-laravel-pint#79

[calebdw]

@saade, that means that there's input on STDIN when vscode is trying to run pint

[crynobone]

As this is currently breaking for PHPStorm and VSCode I believe we should revert it for now and work to either:

1. have this integrated in next major release
2. Use --stdout and optional --no-stdout to avoid breaking changes

[calebdw]

There's already a fix on the other side, the problem is that they have stdin open when it should not be

[crynobone]

@calebdw can you share the link to progress on PHPStorm and VSCode?

[calebdw]

open-southeners/vscode-laravel-pint#79 (comment)

[crynobone]

for PHPStorm? This is still a big issue for developers running on PHPStorm

[calebdw]

I haven't seen any mention of PHPStorm and no one I know that uses PHPStorm has said anything about pint not working

[crynobone]

See #401

[calebdw]

Hmmm, I suppose you could add a --stdin flag but that's really on them---you should not be calling a cli tool with stdin open if you don't want the tool to potential react to that input

[crynobone]

This reverted for now, and as suggested earlier:

1. Have this integrated in next major release (PR to develop branch)
2. Use --stdin to enable stdin when available and the optional --no-stdin (default)
3. Other suggestions that avoid breaking changes are welcomed

This gives IDE and IDE plugins developers time to support the new feature without locking everyone on an old version.