Perform direct asset name comparison

[tonerdo]

Description

Handle situations where the release asset name contains regex symbols that could mess up matching.

Documentation

TODOs

Please ensure all of these TODOs are completed before asking for a review.

• Ensure the branch is named correctly with the issue number. e.g: feature/new-vpc-endpoints-955 or bug/missing-count-param-434.
• Update the docs.
• Keep the changes backward compatible where possible.
• Run the pre-commit checks successfully.
• Run the relevant tests successfully.
• Ensure any 3rd party code adheres with our license policy or delete this line if its not applicable.

Related Issues

Fixes #93

[rhoboat]

I kicked off the build and it passed on CI!

[brikis98]

Thx for the PR! Could you add some testing around this so it doesn't break again in the future? Would be good to test with various names too as a check this really fixes the issue.

[tonerdo]

@brikis98 is there a repo where it'll be okay to upload multiple release assets to help with testing? I don't want to pollute any of our actual repos.

[rhoboat]

It would make sense to use these:
https://github.com/gruntwork-io/fetch-test-public
https://github.com/gruntwork-io/fetch-test-private

Do you have access to these @tonerdo ? (credit to @yorinasub17)

[tonerdo]

@rhoboat I don't have access to create new releases on https://github.com/gruntwork-io/fetch-test-public. I don't have access to https://github.com/gruntwork-io/fetch-test-private at all

[tonerdo]

@brikis98 I was only able to add a test for an asset with the + sign. Good thing is that when I try to upload files containing other regex characters, GitHub simply converts them to ..