fix(analytics): implement Equatable to UserInfo model for unit test purpose

.github/GIT_RULES.md

@@ -0,0 +1,212 @@
+## <span style="color:DarkGoldenRod">Commit Rules:</span>
+This commits rules is set to ensure all the developers follows a uniform way of writing commits so that it is easy to read the changes made and also automate versioning.
+The commits are based on [conventional commit](https://www.conventionalcommits.org/en/v1.0.0/) which is a widely followed convention for commits. While writing a commit message to any changes made to code base, make sure it reflects the changes and follows the conventions i.e:
+
+```
+change_type(package_name): short description/subject line...
+
+Long Description...
+```
+
+Here,
+
+change_type means the type of changes like `feat`,`fix` and so on.
+
+package_name means which packages this changes is for. This is optional.
+
+short discription/subject line means about the changes
+
+Long Description are optional. Add it if its required to reflect the changes in more detail.
+
+For eg:
+
+Lets say the changes is about implementing a new feature which is about new social login mechanism in `deriv_auth` package.
+
+```
+feat(deriv_auth): add UI for sign in page
+
+- create reusable text field using global app theme
+- add bloc for sign in logic implementation
+- add google services for authentication
+```
+<b>More changes types:</b>
+| Changes Types | Meaning                    | Description                                                                                                   |
+| ------------- | -------------------------- | ------------------------------------------------------------------------------------------------------------- |
+| feat          | Features                   | A new feature                                                                                                 |
+| fix           | Bug Fixes                  | A bug fix                                                                                                     |
+| chore         | Chores                     | Other changes that don’t modify src or test files                                                             |
+| docs          | Docume­ntation             | Docume­ntation only changes                                                                                   |
+| revert        | Reverts                    | Reverts a previous commit                                                                                     |
+| refactor      | Code Refact­oring          | A code change that neither fixes a bug nor adds a feature                                                     |
+| test          | Tests                      | Adding missing tests or correcting existing tests                                                             |
+| style         | Styles                     | Changes that do not affect the meaning of the code (white­ -space, format­ting, missing semi-c­olons, etc)    |
+| perf          | Perfor­mance Improv­ements | A code change that improves perfor­mance                                                                      |
+| build         | Builds                     | Changes that affect the build system or external depend­encies (example scopes: gulp, broccoli, npm)          |
+| ci            | Continuous Integr­ations   | Changes to our CI config­uration files and scripts (example scopes: Travis, Circle, Browse­rStack, SauceLabs) |
+
+Optional: If you would like to pre populate your commit box with the commit template then you can do it by adding `.gitmessage` inside `.github` folder to commit template for that project with the following command.(Note: This won't work if you write commit via terminal.)
+
+`git config commit.template "YOUR_PROJECT_PATH/.github/.gitmessage"`
+
+### Examples
+* ```
+  feat: add email notifications on new direct messages
+  ```
+* ```
+  feat(shopping cart): add the amazing button
+  ```
+* ```
+  feat!: remove ticket list endpoint
+
+  refers to JIRA-1337
+
+  BREAKING CHANGES: ticket enpoints no longer supports list all entites.
+  ```
+* ```
+  fix(api): handle empty message in request body
+  ```
+* ```
+  fix(api): fix wrong calculation of request body checksum
+  ```
+* ```
+  fix: add missing parameter to service call
+
+  The error occurred because of <reasons>.
+  ```
+* ```
+  perf: decrease memory footprint for determine uniqe visitors by using HyperLogLog
+  ```
+* ```
+  build: update dependencies
+  ```
+* ```
+  build(release): `bump version to 1.0.0
+  ```
+* ```
+  refactor: implement fibonacci number calculation as recursion
+  ```
+* ```
+  style: remove empty line
+  ```
+### <span style="color:Crimson">Breaking Changes Indicator</span>
+Breaking changes should be indicated by an 
+<span style="color:red;font-size:2em"> ! </span> 
+before the `:` in the subject line e.g. `feat(api)!: remove status endpoint`
+* Is an **optional** part of the format
+
+
+<p>&nbsp;</p>
+
+## <span style="color:DarkGoldenRod">Semantic versioning:
+<center><span style="color:lime; font-size: 4em;">1 . 4 . 3 + 2</span></center>
+<center><span style="color:green; font-size: 2em;">Major . Minor . Patch + build</span></center>
+<p>&nbsp;</p>
+
+<b><span style="color:orange">Major Release:</span></b>
+If a ```“breaking change”``` is introduced, the major release number must be increased
+
+```
+feat(api)!: remove status endpoint
+fix!: bug fix with breaking change
+```
+
+<b><span style="color:orange">Minor Release:</span></b>
+New features have been introduced, which are backwards compatible ```no “breaking changes”```
+
+
+```
+feat: new feature
+```
+
+<b><span style="color:orange">Patch Release: </span></b>
+Bug fixes ```no “breaking changes”```</br>
+```
+fix: something in code
+refactor: code changes that doesn't fix or add anything
+```
+
+<b><span style="color:orange">Build:</span></b> This number is optional and can be used to differentiate between different builds of the same version.
+</br>
+
+<b>no change <span style="color:orange">| | </span>build bump:</b>
+```
+build, chore, ci, docs, style, perf, test
+```
+<p>&nbsp;</p>
+
+## <span style="color:DarkGoldenRod">PR Rules:</span>
+
+This Rules is set to create a uniform way of submitting Pull requests where all the necessary information for the changes are listed in the title, or description. There is a standard template for creating PR. When you are creating a PR to any repo always make sure:
+
+- you have titled it following conventional pattern and also included all the necessary information in it.
+  for eg:
+  Title: `feat(deriv_auth): [MOBC-299] Add ability to sign in with google`
+
+  Here,</br> The title defines:
+
+  - what type the changes/PR is about like feature, bug fixes, documentations, refactor. </br>
+  - which package/app is this PR for.(optional) </br>
+  - the clickup card id - short title that describes the changes </br>
+
+- you have added detailed description that gives enough information about the PR.
+- you have commits only relevant to your changes and not other's commit which shouldn't be there.
+
+  Also, it is always better to squash commits that are only relevant to any particular PR. Such as changes requested through PR review. If these changes does not reflects any really meaning or value in the main project history then it is always better to squash such commits into one. It helps to maintain a clean commit history.
+
+  **The template looks something like this:**
+
+        <!-- Please refer to this [guide](https://github.com/regentmarkets/flutter-deriv-packages/blob/master/.github/GIT_RULES.md#pr-rules) for any confusion while creating the PR -->
+
+        **Clickup link:** <!-- Add your clickup link here, Remove this line if this PR is not for a task -->
+        **Fixes issue:** #<!-- Issue number here, Remove this line if this PR isn't related to any issue -->
+
+        This PR contains the following changes:
+
+        <!-- Provide a description or list of changes -->
+
+        - [ ] ✨ New feature (non-breaking change which adds functionality)
+        - [ ] 🛠️ Bug fix (non-breaking change which fixes an issue)
+        - [ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
+        - [ ] 🧹 Code refactor
+        - [ ] ✅ Build configuration change
+        - [ ] 📝 Documentation
+        - [ ] 🗑️ Chore
+
+        ### Developers Note (Optional)
+
+        <!-- REMOVE THIS SECTION IF IT IS NOT NEEDED.>
+
+        <!-- Add the reason of making changes in this approach so that it will be helpful to reviewers while reviewing it. -->
+
+        ## Pre-launch Checklist (For PR creator)
+
+        As a creator of this PR:
+
+        <!-- Put an `x` in all the boxes that apply ([x]) -->
+
+        - [ ] ✍️ I have included clickup id and package/app_name in the PR title. <!-- Find the guide [here](https://github.com/regentmarkets/flutter-deriv-packages/blob/master/.github/GIT_RULES.md#pr-rules) -->
+        - [ ] 👁️ I have gone through the code and removed any temporary changes (commented lines, prints, debug statements etc.).
+        - [ ] ⚒️ I have fixed any errors/warnings shown by the analyzer/linter.
+        - [ ] 📝 I have added documentation, comments and logging wherever required.
+        - [ ] 🧪 I have added necessary tests for these changes.
+        - [ ] 🔎 I have ensured all existing tests are passing.
+
+        ## Reviewers
+
+        <!-- Tag the reviewers of this PR -->
+
+        ## Pre-launch Checklist (For Reviewers)
+
+        As a reviewer I ensure that:
+
+        - [ ] ✴️ This PR follows the standard PR template.
+        - [ ] ✴️ The information in this PR properly reflects the code changes.
+        - [ ] 🧪 All the necessary tests for this PR's are passing.
+
+        ## Pre-launch Checklist (For QA)
+
+        - [ ] 👌 It passes the acceptance criteria.
+
+        ## Pre-launch Checklist (For Maintainer)
+
+        - [ ] [MAINTAINER_NAME] I make sure this PR fulfills its purpose.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,69 @@
+---
+name: ⚠️ Bug Report
+about: Create a report to help us improve our packages, including regressions
+title: '⚠️ [Package Name] - Brief description of the issue'
+labels: 'bug'
+assignees: ''
+
+---
+
+### Prerequisites to Check
+
+- Have you checked that this issue hasn't been already reported?
+- Are you using the latest version of our package?
+- Have you checked the documentation for this feature/issue?
+
+### Issue Type
+
+- [ ] General Bug
+- [ ] Regression
+
+If this is a regression, please provide:
+- Previous package version where the feature worked:
+- Current package version where the regression occurs:
+
+### Package Version and Flutter Environment
+
+- Package Version: 
+- Flutter (Output of `flutter doctor`):
+
+### Affected Application(s)
+
+- [ ] Deriv Go
+- [ ] Deriv P2P
+- [ ] Both
+- [ ] Not Applicable
+
+### Description
+
+Briefly describe the issue you are experiencing. Include any error messages or screenshots that can help understand the problem. For regressions, describe what functionality is affected and how the behavior has changed from previous versions.
+
+### Steps to Reproduce
+
+1. Step one to reproduce
+2. Step two...
+3. (and so on)
+
+### Expected Behavior
+
+What did you expect to happen? For regressions, describe what the correct behavior should be, as it was in the previous working versions.
+
+### Actual Behavior
+
+What actually happened? Explain the current behavior that you consider a bug or a regression.
+
+### Code Snippet
+
+```dart
+// If possible, please provide a code snippet that demonstrates the issue.
+```
+
+### Can this issue be consistently reproduced?
+
+- [ ] Yes
+- [ ] No
+- [ ] Not applicable
+
+### Additional Information
+
+Any additional information, configuration, or data that might be necessary to reproduce the issue.

.github/ISSUE_TEMPLATE/documentation_update_request.md

@@ -0,0 +1,35 @@
+---
+name: 📚 Documentation Update Request
+about: Suggest improvements or report issues in the documentation
+title: '📚 [Docs][Package Name] Summary of the request'
+labels: 'documentation'
+assignees: ''
+
+---
+
+### Documentation Scope
+
+- [ ] General Documentation (repository-level README.md)
+- [ ] Specific Package Documentation (Please ensure the package name is included in the title above)
+
+### Documentation Location
+
+Provide a link or reference to the documentation page or section in question. If this is about a specific package's documentation, please include the path or link to the specific `README.md` file.
+
+### Is this an issue, improvement, or expansion request?
+
+- [ ] Issue - The documentation is incorrect or misleading
+- [ ] Improvement - The documentation could be clearer or more detailed
+- [ ] Expansion - Additional information or topics are needed
+
+### Describe the problem or your suggestion
+
+A clear and concise description of the issue you found or the improvement you are suggesting. If you are reporting an inaccuracy, please describe what is wrong or misleading.
+
+### Proposed Changes
+
+If you have specific ideas on how to improve or correct the documentation, please outline them here. Include text snippets, markdown, or any other content that you think should be included or modified.
+
+### Additional context
+
+Add any other context about the problem or your suggestion here, such as why the change is important or how it would benefit users of the documentation.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,40 @@
+---
+name: 🚀 Feature Request
+about: Suggest a new feature or a new package
+title: '🚀 [Feature/Package] Short description'
+labels: 'enhancement'
+assignees: ''
+
+---
+
+### Request Type
+
+- [ ] New Feature in Existing Package
+- [ ] New Package Request
+
+### Is your feature request related to a problem? Please describe.
+
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+### Describe the solution you'd like
+
+A clear and concise description of what you want to happen. If you are proposing a new package, please explain the purpose and potential functionalities.
+
+### Describe alternatives you've considered
+
+A clear and concise description of any alternative solutions or features you've considered.
+
+### Affected Package(s)
+
+If this is about a new feature in an existing package, please specify the package(s). If this is a new package request, mention 'N/A' or 'New Package'.
+
+### Affected Application(s)
+
+- [ ] Deriv Go
+- [ ] Deriv P2P
+- [ ] Both
+- [ ] Not Applicable
+
+### Additional context
+
+Add any other context, mockups, diagrams, or code snippets about the feature request here.