Updated webhook subscription topic constants

[kisuka]

WHY are these changes introduced?

Currently you cannot use a large number of webhook topics using the current method of constants. This is due to them not being present within the Topics.php file.

WHAT is this pull request doing?

Adds missing webhook subscription topic constants to match the current list for 2024-07 located here:
https://shopify.dev/docs/api/admin-graphql/2024-07/enums/webhooksubscriptiontopic

Type of change

• Patch: Bug (non-breaking change which fixes an issue)
• Minor: New feature (non-breaking change which adds functionality)
• Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• I have added a changelog entry, prefixed by the type of change noted above
• I have added/updated tests for this change
• I have updated the documentation for public APIs from the library (if applicable)

[kisuka]

I have signed the CLA

[lizkenyon]

Hi there 👋

First off big thank you for your contribution!

Could you add a changelog entry for this change?

Secondly were you finding that you were getting errors when you were passing in these topics as a string instead of using the constant?
Our hope is that you should be able to use either, so if there is a place throwing an error when using a string, (and then forces us to have to update these constants when a new topic is released), I want to resolve that as well.

[kisuka]

@lizkenyon No problem. Added the changelog entry. Wasn't getting any issues when using strings instead of constants, just figured it should probably remain consistent if historically they've been used and are in the codebase.

[lizkenyon]

@lizkenyon No problem. Added the changelog entry. Wasn't getting any issues when using strings instead of constants, just figured it should probably remain consistent if historically they've been used and are in the codebase.

Perfect! I agree we should definitely have these.

It looks like there are a few linting errors that are causing the CI to fail. Once you resolve those we can get this merged.

[kisuka]

@lizkenyon No problem. Added the changelog entry. Wasn't getting any issues when using strings instead of constants, just figured it should probably remain consistent if historically they've been used and are in the codebase.

Perfect! I agree we should definitely have these.

It looks like there are a few linting errors that are causing the CI to fail. Once you resolve those we can get this merged.

Done :) Lemme know if that method of multi-line is okay or if there's another practice that should be followed.