RUMM-1467 Remove deprecation warnings when compiling the SDK code

[ncreated]

What and why?

🧽 This PR cleans up compiler warnings which pop up when compiling the SDK:

These warnings appear to any user linking the SDK to their project. Their presence is misleading - the user is not using any deprecated API, instead we do it internally in the SDK code. Because the user can't do anything to dismiss it, I'm fixing it in this PR by removing deprecation annotation in these APIs. This operation is safe as explained below.

How?

These warnings were introduced in #523 by marking legacy cases as deprecated in 3 enums:

public enum LogsEndpoint {
   // ...
}
public enum TracesEndpoint {
   // ...
}
public enum RUMEndpoint {
   // ...
}

This isn't required, as those endpoints can only be used in these 3 legacy APIs which (if called) will already emit the deprecation warning:

@available(*, deprecated, message: "This option is replaced by `set(endpoint:)`. Refer to the new API comment for details.")
public func set(logsEndpoint: LogsEndpoint) -> Builder { /* ... */ }

@available(*, deprecated, message: "This option is replaced by `set(endpoint:)`. Refer to the new API comment for details.")
public func set(tracesEndpoint: TracesEndpoint) -> Builder { /* ... */ }

@available(*, deprecated, message: "This option is replaced by `set(endpoint:)`. Refer to the new API comment for details.")
public func set(rumEndpoint: RUMEndpoint) -> Builder { /* ... */ }

All these APIs are already replaced with a single set(endpoint:) which receives DatadogEndpoint enum.

Review checklist

• Feature or bugfix MUST have appropriate tests (unit, integration)
• Make sure each commit and the PR mention the Issue number or JIRA reference