chore(asm): update release note for New Application Security Events Tracking API (#4958)

## Description
Make release note more clear as per @juanjux 's work. Original PR:
#4913

## Checklist
- [x] Followed the [library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/contributing.html#Release-Note-Guidelines)
when writing a release note.
- [x] Add additional sections for `feat` and `fix` pull requests.
- [x] [Library
documentation](https://github.com/DataDog/dd-trace-py/tree/1.x/docs)
and/or [Datadog's documentation
site](https://github.com/DataDog/documentation/) is updated. Link to doc
PR in description.

<!-- Copy and paste the relevant snippet based on the type of pull
request -->

<!-- START feat -->

## Motivation
<!-- Expand on why the change is required, include relevant context for
reviewers -->

## Design 
<!-- Include benefits from the change as well as possible drawbacks and
trade-offs -->

## Testing strategy
<!-- Describe the automated tests and/or the steps for manual testing.

<!-- END feat -->

<!-- START fix -->

## Relevant issue(s)
<!-- Link the pull request to any issues related to the fix. Use
keywords for links to automate closing the issues once the pull request
is merged. -->

## Testing strategy
<!-- Describe any added regression tests and/or the manual testing
performed. -->

<!-- END fix -->

## Reviewer Checklist
- [ ] Title is accurate.
- [ ] Description motivates each change.
- [ ] No unnecessary changes were introduced in this PR.
- [ ] Avoid breaking
[API](https://ddtrace.readthedocs.io/en/stable/versioning.html#interfaces)
changes unless absolutely necessary.
- [ ] Tests provided or description of manual testing performed is
included in the code or PR.
- [ ] Release note has been added and follows the [library release note
guidelines](https://ddtrace.readthedocs.io/en/stable/contributing.html#Release-Note-Guidelines),
or else `changelog/no-changelog` label added.
- [ ] All relevant GitHub issues are correctly linked.
- [ ] Change contains telemetry where appropriate (logs, metrics, etc.).
- [ ] Telemetry is meaningful, actionable and does not have the
potential to leak sensitive data.

Author: ZStriker19

releasenotes/notes/asm-event-tracking-sdk-d7e8516511c73589.yaml

@@ -1,4 +1,8 @@
 ---
 features:
   - |
-    ASM: Added three new functions for the Application Security Events Tracking API in the `appsec.trace_utils` module; `track_user_login_success_event`, `appsec.track_user_login_failure_event` and `track_custom_event`.
+    ASM: New Application Security Events Tracking API, starting with the functions ``track_user_login_success_event`` and
+     ``track_user_login_failure_event`` for tracking user logins (it will also internally call ``set_user``) and ``track_custom_event`` for any custom events. 
+     You can find these functions in the ``ddtrace.appsec.trace_utils`` module. Calling these functions will create new tags under the ``appsec.events`` 
+     namespace (``appsec.events.user.login`` for logins) allowing you to track these events with Datadog. In the future this will 
+     be used to provide protection against account takeover attacks (ATO). Public documentation will be online soon.