Run module publish action only on the main repo

[onursumer]

Fix cBioPortal/cbioportal/issues/6970

Checks

• Has tests or has a separate issue that describes the types of test that should be created. If no test is included it should explicitly be mentioned in the PR why there is no test.
• The commit log is comprehensible. It follows 7 rules of great commit messages. For most PRs a single commit should suffice, in some cases multiple topical commits can be useful. During review it is ok to see tiny commits (e.g. Fix reviewer comments), but right before the code gets merged to master or rc branch, any such commits should be squashed since they are useless to the other developers. Definitely avoid merge commits, use rebase instead.
• Is this PR adding logic based on one or more clinical attributes? If yes, please make sure validation for this attribute is also present in the data validation / data loading layers (in backend repo) and documented in File-Formats Clinical data section!

[zhx828]

Just a note: this is under assumption that no one has NODE_AUTH_TOKEN except the people actually wants to publish it.

[onursumer]

Seems like there is some sort of placeholder for NODE_AUTH_TOKEN under forked repos as well. So, this check does NOT work. We need to come up with a better solution.

[onursumer]

Now using a job level conditional within the workflow yaml file. It seems tricky to check secret variables, so for now just checking the repository name.

[inodb]

Nice find 👍