Min & Max event severity definable in model for events

[thompson-tomo]

Is your feature request related to a problem? Please describe.
I want to have a consistent understanding of what severity level should be used for events.

Describe the solution you'd like
The ability to set both the min & Max severity levels for events so that instrumentation can use them in a consistent manner.

Describe alternatives you've considered

• Setting an explicit severity level number but too subjective and difficult to quantify the levels
• Setting an explicit severity level text ie info but too restrictive for scenarios where an error is also potentially captured

Additional context

• https://github.com/instrumentation-score/spec/blob/main/rules/LOG-002.md
• https://cloud-native.slack.com/archives/C062HUREGUV/p1762896560429319

_{Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[jsuereth]

We think we may want to go the direction of providing a "default" severity vs. min/max. We definitely want the ability to enforce that severity exists on logs and, at a minimum, warn about logs that do not have severity.

[thompson-tomo]

The hard part with default is how we can describe that level when it might be info but changes to error if error.type is set.