docs: Update logic placement guidelines in API architecture (#17234)

This section was using RFC 2119 requirement levels in a strange way.
These levels are meant to designate requirement levels, but here, they
were using to describe technical details of data processing features.

My change removes the strangely-used "**MUST**" specifiers from the
examples of changes that need to live in the SDK, instead using generic
"needs to" phrasing

Author: szokeasaurusrex

develop-docs/sdk/getting-started/standards/api-architecture.mdx

@@ -26,10 +26,10 @@ When deciding where new logic should live, default to server-side (Relay). Proce
 
 Put logic in the SDK only when it genuinely needs to run client-side:
 
-- It **MUST** run before data leaves the customer's application (e.g., user-controlled filtering like `before_send_*`)
+- It needs to run before data leaves the customer's application (e.g., user-controlled filtering like `before_send_*`)
 - It requires access to platform-specific APIs
 - It's strictly latency-sensitive
-- It **MUST** function in offline scenarios
+- It needs to function in offline scenarios
 
 If data has already been collected, transform it in Relay.