docs(js): Review and update Connect Quick Start guide (#14294)

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

## DESCRIBE YOUR PR
Reviewed and updated the Connect Quick Start guide 

Closes: #14288 

## 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)

## EXTRA RESOURCES

- [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)

---------

Co-authored-by: Alex Krawiec <[email protected]>

Author: 2 people

docs/platforms/javascript/guides/connect/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Connect
-description: "Learn about using Sentry with Connect."
+description: "Learn how to manually set up Sentry in your Connect app and capture your first errors."
 sdk: sentry.javascript.node
 fallbackGuide: javascript.node
 categories:
@@ -9,8 +9,4 @@ categories:
   - server-node
 ---
 
-<PlatformContent includePath="getting-started-primer" />
-
-This guide explains how to set up Sentry in your Connect application.
-
 <PlatformContent includePath="getting-started-node" />

platform-includes/getting-started-features-expandable/javascript.node.mdx

@@ -7,5 +7,8 @@
   impact of errors across multiple systems. For example, distributed tracing
   allows you to follow a request from the frontend to the backend and back.
 - [**Profiling**](/product/explore/profiling/): Gain deeper insight than traditional tracing without custom instrumentation, letting you discover slow-to-execute or resource-intensive functions in your app.
+- [**Logs**](/product/explore/logs): Centralize and analyze your application logs to
+  correlate them with errors and performance issues. Search, filter, and
+  visualize log data to understand what's happening in your applications.
 
 </Expandable>

platform-includes/getting-started-verify/javascript.connect.mdx

@@ -1,5 +1,32 @@
+### Issues
+
+First, let's make sure Sentry is correctly capturing errors and creating issues in your project. Add the following code snippet to your main application file; it defines a route that will deliberately trigger an error when called:
+
 ```javascript
-app.get("/debug-sentry", function mainHandler(req, res) {
+app.use("/debug-sentry", (req, res) => {
   throw new Error("My first Sentry error!");
 });
 ```
+
+<OnboardingOption optionId="performance">
+
+### Tracing
+
+To test your tracing configuration, update the previous code snippet by starting a trace to measure the time it takes to execute your code:
+
+```javascript
+app.use("/debug-sentry", async (req, res) => {
+  await Sentry.startSpan(
+    {
+      op: "test",
+      name: "My First Test Transaction",
+    },
+    async () => {
+      await new Promise((resolve) => setTimeout(resolve, 100));
+      throw new Error("My first Sentry error!");
+    }
+  );
+});
+```
+
+</OnboardingOption>