feat(android): Merge Manual Setup and Manual Configuration pages (#16329)

<!-- Use this checklist to make sure your PR is ready for merge. You may
delete any sections you don't need. -->

## DESCRIBE YOUR PR
Merge Manual Setup and Manual Configuration pages into one, otherwise
they were scattered across different sections and very hard to follow

## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [ ] Other deadline: <!-- ENTER DATE HERE -->
- [x] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've
added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [ ] Checked Vercel preview for correctness, including links
- [ ] PR was reviewed and approved by any necessary SMEs (subject matter
experts)
- [ ] PR was reviewed and approved by a member of the [Sentry docs
team](https://github.com/orgs/getsentry/teams/docs)

---------

Co-authored-by: Alex Krawiec <alex.krawiec@sentry.io>

Author: romtsn

docs/platforms/android/configuration/manual-init.mdx

@@ -172,7 +172,7 @@ Alternatively, you can customize the event and scrub the data yourself.
 
 ### Customize or Drop the Error Event
 
-To customize or drop the error event, you'll need to do a [manual initialization](/platforms/android/configuration/manual-init/#manual-initialization) of the Sentry Android SDK. The captured error event can then be customized or dropped with a `BeforeSendCallback`:
+To customize or drop the error event, you'll need to do a [manual initialization](/platforms/android/manual-setup/#configuration-via-sentryoptions) of the Sentry Android SDK. The captured error event can then be customized or dropped with a `BeforeSendCallback`:
 
 ```kotlin
 import io.sentry.android.core.SentryAndroid

docs/platforms/android/integrations/apollo3/index.mdx

@@ -42,7 +42,7 @@ However, you can still override the default behaviour by adding your own instanc
 
 ### Install
 
-To add the Fragment integration, [manually initialize](/platforms/android/configuration/manual-init/#manual-initialization) the Android SDK, then add the `sentry-android-fragment` dependency. Using Gradle:
+To add the Fragment integration, [manually initialize](/platforms/android/manual-setup/#configuration-via-sentryoptions) the Android SDK, then add the `sentry-android-fragment` dependency. Using Gradle:
 
 ```groovy
 implementation 'io.sentry:sentry-android:{{@inject packages.version('sentry.java.android', '5.1.0') }}'

docs/platforms/android/integrations/fragment/index.mdx

@@ -101,7 +101,7 @@ This feature is disabled by default, but you can enable it the following ways.
 
 #### Using `SentryOptions`
 
-If you initialize the SDK [manually as mentioned here](/platforms/android/configuration/manual-init/#manual-initialization), you can enable user interactions like this:
+If you initialize the SDK [manually as mentioned here](/platforms/android/manual-setup/#configuration-via-sentryoptions), you can enable user interactions like this:
 
 ```kotlin {filename:MyApplication.kt}
 SentryAndroid.init(this) { options ->
@@ -330,7 +330,7 @@ fun Second() {
 
 ## Customize the Recorded Breadcrumb/Transaction
 
-By default, the Navigation integration captures route arguments as additional data on breadcrumbs and transactions. In case the arguments contain any PII data, you can strip it out by way of `BeforeBreadcrumbCallback` and `EventProcessor` respectively. To do that, [manually initialize](/platforms/android/configuration/manual-init/#manual-initialization) the SDK and add the following snippet:
+By default, the Navigation integration captures route arguments as additional data on breadcrumbs and transactions. In case the arguments contain any PII data, you can strip it out by way of `BeforeBreadcrumbCallback` and `EventProcessor` respectively. To do that, [manually initialize](/platforms/android/manual-setup/#configuration-via-sentryoptions) the SDK and add the following snippet:
 
 ```kotlin
 import io.sentry.EventProcessor

docs/platforms/android/integrations/jetpack-compose/index.mdx

@@ -155,7 +155,7 @@ Those events are searchable and you can set alerts on them if you use the `http.
 
 ### Customize or Drop the Error Event
 
-To customize or drop the error event, you need to do a [manual initialization](/platforms/android/configuration/manual-init/#manual-initialization) of the Sentry Android SDK.
+To customize or drop the error event, you need to do a [manual initialization](/platforms/android/manual-setup/#configuration-via-sentryoptions) of the Sentry Android SDK.
 
 The captured error event can be customized or dropped with a `BeforeSendCallback`:
 

docs/platforms/android/integrations/ktor-client/index.mdx

@@ -123,7 +123,7 @@ class HomeFragment : Fragment() {
 
 ## Customize the Recorded Breadcrumb/Transaction
 
-By default, the Navigation integration captures route arguments as additional data on breadcrumbs and transactions. In case the arguments contain any PII data, you can strip it out by way of `BeforeBreadcrumbCallback` and `EventProcessor` respectively. To do that, [manually initialize](/platforms/android/configuration/manual-init/#manual-initialization) the SDK and add the following snippet:
+By default, the Navigation integration captures route arguments as additional data on breadcrumbs and transactions. In case the arguments contain any PII data, you can strip it out by way of `BeforeBreadcrumbCallback` and `EventProcessor` respectively. To do that, [manually initialize](/platforms/android/manual-setup/#configuration-via-sentryoptions) the SDK and add the following snippet:
 
 ```kotlin
 import io.sentry.EventProcessor

docs/platforms/android/integrations/navigation/index.mdx

@@ -399,7 +399,7 @@ Those events are searchable and you can set alerts on them if you use the `http.
 
 ### Customize or Drop the Error Event
 
-To customize or drop the error event, you need to do a [manual initialization](/platforms/android/configuration/manual-init/#manual-initialization) of the Sentry Android SDK.
+To customize or drop the error event, you need to do a [manual initialization](/platforms/android/manual-setup/#configuration-via-sentryoptions) of the Sentry Android SDK.
 
 The captured error event can be customized or dropped with a `BeforeSendCallback`:
 

docs/platforms/android/integrations/okhttp/index.mdx

@@ -62,7 +62,7 @@ configurations.configureEach {
 
 ### Install
 
-To add the Timber integration, [manually initialize](/platforms/android/configuration/manual-init/#manual-initialization) the Android SDK, then add the `sentry-android-timber` dependency. Using Gradle:
+To add the Timber integration, [manually initialize](/platforms/android/manual-setup/#configuration-via-sentryoptions) the Android SDK, then add the `sentry-android-timber` dependency. Using Gradle:
 
 ```groovy
 implementation 'io.sentry:sentry-android:{{@inject packages.version('sentry.java.android', '4.2.0') }}'