Update PR template (#473)

## Description

This PR adds the following:
* Clear separation for breaking and non-breaking changes.
* Another type of changes called `Other` for new test cases, general
code style improvements etc.
* Remove `Both Android and iOS` option from bug template since now there
is an option to select both Android and iOS which overlaps this option

### Type of change

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [x] Documentation update (improves or adds clarity to existing
documentation)

### Tested on

- [ ] iOS
- [ ] Android

### Testing instructions

<!-- Provide step-by-step instructions on how to test your changes.
Include setup details if necessary. -->

### Screenshots

<!-- Add screenshots here, if applicable -->

### Related issues

<!-- Link related issues here using #issue-number -->

### Checklist

- [x] I have performed a self-review of my code
- [x] I have commented my code, particularly in hard-to-understand areas
- [x] I have updated the documentation accordingly
- [x] My changes generate no new warnings

### Additional notes

<!-- Include any additional information, assumptions, or context that
reviewers might need to understand this PR. -->

---------

Co-authored-by: Jakub Mroz <115979017+jakmro@users.noreply.github.com>

Author: msluszniak

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -77,7 +77,6 @@ body:
       options:
         - Android
         - iOS
-        - Both Android and iOS
         - Platform agnostic
     validations:
       required: true

.github/pull_request_template.md

@@ -2,12 +2,17 @@
 
 <!-- Provide a concise and descriptive summary of the changes implemented in this PR. -->
 
+### Introduces a breaking change?
+
+- [ ] Yes
+- [ ] No
+
 ### Type of change
 
-- [ ] Bug fix (non-breaking change which fixes an issue)
-- [ ] New feature (non-breaking change which adds functionality)
-- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Bug fix (change which fixes an issue)
+- [ ] New feature (change which adds functionality)
 - [ ] Documentation update (improves or adds clarity to existing documentation)
+- [ ] Other (chores, tests, code style improvements etc.)
 
 ### Tested on