ci(github): update publishing workflows to use github.repository_owner

[adrianbatuto]

Primary Changes

1. Updated publishing workflows to use gitHub.repository_owner variable

Fixes #3597

Pull Request Requirements

• Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

[adrianbatuto]

Adding here the screenshots of the published packages after running the workflows.

[jagpreetsinghsasan]

Looks good to me.
@petermetz does the username hyperledger-ghci remains the same? (We are changing the hyperledger prefix so I think we will need a ticket for that as well once Cacti moves to the new org structure)

[petermetz]

Looks good to me. @petermetz does the username hyperledger-ghci remains the same? (We are changing the hyperledger prefix so I think we will need a ticket for that as well once Cacti moves to the new org structure)

@jagpreetsinghsasan I'm not sure either. Based on the screenshot my guess is that the git username and user email are not actually being used for the authentication with npm at all. So it might be that we can just simply remove them instead modifying them to use the variables. I'm deducing this from the fact that it worked on @adrianbatuto 's fork despite the username being different.

@adrianbatuto I think you can just remove those lines and re-test on your fork and if it can still publish to npm then we are golden.

[adrianbatuto]

Looks good to me. @petermetz does the username hyperledger-ghci remains the same? (We are changing the hyperledger prefix so I think we will need a ticket for that as well once Cacti moves to the new org structure)

@jagpreetsinghsasan I'm not sure either. Based on the screenshot my guess is that the git username and user email are not actually being used for the authentication with npm at all. So it might be that we can just simply remove them instead modifying them to use the variables. I'm deducing this from the fact that it worked on @adrianbatuto 's fork despite the username being different.

@adrianbatuto I think you can just remove those lines and re-test on your fork and if it can still publish to npm then we are golden.

Sorry for the late response, I just got back from leave.
I will look into this and let you know.

[adrianbatuto]

@petermetz I was able to publish successfully after removing the user email and name from the workflow.