chore: Prepare release 1.0.0

[miquelbeltran]

chore: Prepare release 1.0.0

Description 📝

• Purpose: Preparing release 1.0.0
• Approach: Bump version, update changelog and check publish dryrun

Type of change

• release

Updates

• Bump version to 1.0.0
• Update changelog (note: some PRs were not merged using "Squash and merge" so commit history is a bit messy)

Test plan 🧪

Release dryrun:

➜  raygun-cli git:(release/1.0.0) dart pub publish --dry-run
Resolving dependencies... 
Downloading packages... 
Got dependencies!
Publishing raygun_cli 1.0.0 to https://pub.dev:
├── CHANGELOG.md (<1 KB)
├── LICENSE (1 KB)
├── README.md (6 KB)
├── analysis_options.yaml (<1 KB)
├── bin
│   └── raygun_cli.dart (2 KB)
├── example
│   └── main.dart (<1 KB)
├── lib
│   ├── raygun_cli.dart (<1 KB)
│   └── src
│       ├── config_props.dart (1 KB)
│       ├── deployments
│       │   ├── deployments.dart (1 KB)
│       │   ├── deployments_api.dart (1 KB)
│       │   └── deployments_command.dart (1 KB)
│       ├── environment.dart (1 KB)
│       ├── proguard
│       │   ├── proguard.dart (1 KB)
│       │   ├── proguard_api.dart (1 KB)
│       │   └── proguard_command.dart (1 KB)
│       ├── sourcemap
│       │   ├── flutter
│       │   │   └── sourcemap_flutter.dart (1 KB)
│       │   ├── node
│       │   │   └── sourcemap_node.dart (<1 KB)
│       │   ├── sourcemap_api.dart (1 KB)
│       │   ├── sourcemap_base.dart (<1 KB)
│       │   ├── sourcemap_command.dart (1 KB)
│       │   └── sourcemap_single_file.dart (1 KB)
│       └── symbols
│           ├── flutter_symbols.dart (2 KB)
│           └── flutter_symbols_api.dart (2 KB)
├── pubspec.yaml (<1 KB)
├── pull_request_template.md (1 KB)
└── test
    └── config_props_test.dart (3 KB)

Total compressed archive size: 10 KB.
The server may enforce additional checks.

Package has 0 warnings.

Author to check 👓

• Project and all contained modules builds successfully
• Self-/dev-tested
• Unit/UI/Automation/Integration tests provided where applicable
• Code is written to standards
• Appropriate documentation written (code comments, internal docs)

Reviewer to check ✔️

• Project and all contained modules builds successfully
• Change has been dev-/reviewer-tested, where possible
• Unit/UI/Automation/Integration tests provided where applicable
• Code is written to standards
• Appropriate documentation written (code comments, internal docs)

[TheRealAgentK]

Let's go!!!