config: integrate bugsee in flutter template and update build pipeline

[koukibadr]

Proposed Changes

• Bug fix
• Feature
• Code style update (formatting)
• Refactoring (no functional changes, no api changes)
• Build or CI related changes
• Documentation content changes
• Other, please describe:

Description

• Integrate the Bugsee SDK in the Template App project
• Implement Bugsee configuration layout in the Diagnostic module as a new Tab called "Bugsee"
• Integrate manual methods to invoke logging exceptions (logExceptions, showReport)
• Add enable/disable Bugsee report and persisting the user's config in shared prefs.
• Add enable/disable video capturing
• Update the app pipeline to inject the Bugsee token when building the release version

Different Bugsee configuration states in imags:

Impact on version

• Major
  • The template structure was changed.
• Minor
  • New functionalities were added.
• Patch
  • A bug in behavior was fixed.
  • Documentation was changed.

PR Checklist

Always applicable

No matter your changes, these checks always apply.

• Your conventional commits are aligned with the Impact on version section.
• Updated CHANGELOG.md.
  • Use the latest Major.Minor.X header if you do a Patch change.
  • Create a new Major.Minor.X header if you do a Minor or Major change.
  • If you create a new header, it aligns with the Impact on version section and matches what is generated in the build pipeline.
• Documentation files were updated according with the changes.
  • Update README.md and src/cli/CLI.md if you made changes to templating.
  • Update AzurePipelines.md and src/app/README.md if you made changes to pipelines.
  • Update Diagnostics.md if you made changes to diagnostic tools.
  • Update Architecture.md and its diagrams if you made architecture decisions or if you introduced new recipes.
  • ...and so forth: Make sure you update the documentation files associated to the recipes you changed. Review the topics by looking at the content of the doc/ folder.
• Images about the template are referenced from the wiki and added as images in this git.
• TODO comments are hints for next steps for users of the template and not planned work.

Contextual

Based on your changes these checks may not apply.

• Automated tests for the changes have been added/updated.
• Tested on all relevant platforms

Other information

Internal Issue (If applicable):

[jeanplevesque]

You currently have 2 commits, each with the build: conventional commit prefix, however you introduce a new feature and are not only changing code related to the build pipeline so you should at least have a feat: commit.

[jeanplevesque]

The description section of the Pull Request template must be filled.

[Soap-141]

Good job!

[jeanplevesque]

/azp run

[azure-pipelines]

Azure Pipelines failed to run 1 pipeline(s).