Tweak the publication condition to prevent publishing from forked repos

[danicheg]

One might argue that users can use githubWorkflowPublishCond to prevent publishing from forked repos. Sure, but I’m confident this condition should be the default. Adding it manually to the build of dozens of projects isn’t exactly ideal, either.
This is basically the same as what we did in #720, but adding the same SBT setting again just feels a bit extra to me 🤷🏻

[danicheg]

I was just thinking again about adding a dedicated SBT setting for the fork condition. Maybe introducing githubWorkflowForkCondition with a default value of github.event.repository.fork == false isn't such a bad idea — especially if we deprecate the tlCiForkCondition and substitute its default with the newly added githubWorkflowForkCondition. WDYT?

[bpholt]

I think it is a good idea not to publish from forks by default, but I can envision situations where users legitimately would want to do so, so I don't think it should be disabled without a way to re-enable it. A dedicated sbt setting seems reasonable to me.

[armanbilge]

Thank you, this is a really good change. Sorry it took me so long to review. I have just a couple nitpicks.

[danicheg]

Any chance we'd merge this?

[armanbilge]

I'm so sorry—I just realize one more important bikeshed I think.

Currently, githubWorkflowForkCondition == true if the repository is not a fork, which is confusing. (This was the original mistake of tlCiForkCondition).

So either we should call it githubWorkflowNotForkCondition or change the definition to test == true, and then adjust the usecases.