github action to publish to homebrew

[ybeapps]

relates to issue #426

1. this is the workflow
2. @love-linger you need to create a clone (not fork) same repo like in the example in the issue
3. @love-linger you need to create a token that can be used to create a PR from this repo to the new repo
4. integrate the token in the placeholder I left

it should be triggered when a release is created

1. it goes to the new repo
2. grabs a link of the published app based on version and arch
3. download
4. modify the ruby file in the new repo
5. calculate sha
6. create a PR in the new repo

then you need to merge the PR - and it's published :)
I guess you can automate the merge if you like (if specific user creates a PR - auto-merge it)

then you just add the new install via homebrew to Readme :)

[aikawayataro]

Well, in my opinion this is the wrong way to handle this, I believe the cask tap should be querying for updates, not upstream pushing to it. Workflow scheduling and a python script will do the job, I believe 😁
Anyway, there will be no further progress on this topic according to #426 (comment)

And I also believe that users are more than welcome to maintain their own taps/repositories, like @ChiahongHong did. I even think there is a place in README for a note with 3rd party sources

[love-linger]

Sorry, everyone. There's no plan to do this currently.