Bump flutter_reaction_button from 2.0.2 to 3.0.0+2

[palisadoes]

We need to bump flutter_reaction_button in the code base from 2.0.2 to 3.0.0+2.

1. We need to maintain all references to flutter_reaction_button in the code base, and you must use the new non-deprecated approaches in this library to maintain the flutter_reaction_button functionality. Deleting flutter_reaction_button functionality is not an option.
2. You must also ensure that all code base tests pass and are valid. Tests without actual executable code does not benefit the community of users, we have experienced this unfortunate fact in the past.
3. The overall code coverage level must be maintained.

Release notes for v3.0.0+2

Sourced from flutter_reaction_button's releases.

v3.0.0

BREAKING CHANGES:

• FlutterReactionButton and FlutterReactionButtonToggle replaced by ReactionButton
• itemSize is required in ReactionButton
• onReactionChanged callback updated
• VerticalPosition and HorizontalPosition removed

What's New:

• Use overlay instead of navigator
• Adds child to ReactionButton
• Animated ReactionsBox

Changelog

Sourced from flutter_reaction_button's changelog.

3.0.0+2

• Minor updates

3.0.0+1

• Update README

3.0.0

• BREAKING CHANGE:
  • FlutterReactionButton and FlutterReactionButtonToggle removed
  • itemSize is required in ReactionButton
  • onReactionChanged callback updated
  • VerticalPosition and HorizontalPosition removed
• Adds child to ReactionButton
• Animated ReactionsBox

Commits

• 8132578 feat: update CHNAGELOG.md
• 72f2c0b feat: update pubspec.yaml
• a8ebd81 feat: remove unused resources
• a40b15f Merge branch 'feature/overlay' of https://github.com/GeekAbdelouahed/flutter-...
• 439ae8d feat: update workflows
• 9e9b501 Update CHANGELOG.md
• 37b73f6 feat: update pubspec.yaml
• 1e50dc6 feat: update CHANGELOG.md
• cb50276 feat: remove mouse region
• cfd0234 feat: remove unused resources
• Additional commits viewable in compare view

[Azad99-9]

@palisadoes could you please assign this issue to me.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.