feat: add release and dist to sourcemaps upload command

[buenaflor]

📜 Description

Allows bundles to be associated so it shows up in the sourcemaps site, this does not affect symbolication - this is only informational

💡 Motivation and Context

Closes #330

💚 How did you test it?

Manually tested E2E & test suite that checks that the correct commands are executed

📝 Checklist

• I reviewed submitted code
• I added tests to verify changes
• I updated the docs if needed
• All tests passing
• No breaking changes

🔮 Next steps

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against 9659c67

[buenaflor]

@denrase I guess this is semantics but if we automatically pick up a release from pubspec e.g 1.0.0+1

should we then during sourcemaps upload:

• set release to 1.0.0+1 and dist to 1
• or set release to 1.0.0 and dist to 1
• or only set release to 1.0.0+1 because it has a build number already?

It's not really important because it's only for informational purposes (see screenshot), but I guess we should align anyway

[buenaflor]

Let's keep it as it is right now, it's only informational anyway. If someone is confused by it in the future we can revisit again