Mention obfuscate debug symbols for Flutter (#5644)

Author: marandaneto

src/platforms/flutter/troubleshooting.mdx

@@ -10,7 +10,7 @@ If you need help solving issues with Sentry's Flutter SDK, you can read the edge
 
 ## Known Limitations
 
-- If you enable the `split-debug-info` feature, you must upload the Debug Symbols manually.
+- If you enable the `split-debug-info` and `obfuscate` features, you must upload [debug symbols](/platforms/flutter/upload-debug/).
 - Issue titles might be obfuscated as we rely on the `runtimeType`, but they may not be human-readable. See the [Obfuscate Caveat](https://flutter.dev/docs/deployment/obfuscate#caveat).
 - Layout related errors are only caught by [FlutterError.onError](https://api.flutter.dev/flutter/foundation/FlutterError/onError.html) in debug mode. In release mode, they are removed by the Flutter framework. See [Flutter build modes](https://flutter.dev/docs/testing/build-modes).
 - On Windows, you have to set the version and build number manually, see [this issue on GitHub](https://github.com/flutter/flutter/issues/73652). To do so:

src/platforms/flutter/upload-debug.mdx

@@ -12,8 +12,6 @@ With default settings, complete stack traces are available in your Dart error, o
 
 <Note>
 
-For Flutter iOS `split-debug-info` and `obfuscate` flags are not supported. This is a known tooling limitation, as discussed in [43612](https://github.com/dart-lang/sdk/issues/43612) and [43274](https://github.com/dart-lang/sdk/issues/43274).
-
 For Flutter Desktop (Windows/macOS/Linux) `split-debug-info` and `obfuscate` flags are not supported yet. See this [issue](https://github.com/getsentry/sentry-dart/issues/433).
 
 </Note>