Towards stabilization of https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/events.md

Fixes #1651

Changes

This PR refines the documentation for general event semantics to improve clarity and structure.

Documentation improvements

• Restructure event semantics section for better readability
• Consolidate event name definition with its uniquely identifying role
• Simplify cardinality and naming guidelines into single concise statement

Requirement level clarifications

• Attributes: Strengthen from MAY to SHOULD to emphasize their importance for providing event context
• Severity number: Strengthen from MAY to SHOULD to encourage consistent severity tracking
• Remove explicit "body MAY be present" statement (still implied in first bullet) given unclear use cases. Body SHOULD NOT be used.

Technical changes

• Consistent hyperlinking to all specification fields (event name, attributes, body, severity number)
• Align with RFC 2119 keyword usage patterns (use SHOULD instead of RECOMMENDED)
• Improve consistency with naming guidelines reference
• Enhanced external event compatibility guidance with explicit instrumentation SHOULD

Rationale

The changes improve developer experience by:

1. Making requirements clearer and easier to scan
2. Emphasizing best practices (using attributes and severity numbers)
3. Reducing redundancy while maintaining completeness
4. Better aligning with the structure used in other semantic convention documents
5. Providing more concise and actionable guidance for convention authors