(DOCSP-43465) Incorrect information about Trigger changestream behavior in relation to Atlas clusters (#861)

## Pull Request Info

Our [Triggers
docs](https://www.mongodb.com/docs/atlas/app-services/triggers/database-triggers/)
have the following note about database triggers:

"Your app opens a single change stream for each collection with at least
one enabled trigger. If multiple triggers are enabled for a collection
they all share the same change stream."

This is not correct. We actually go in almost the opposite direction. We
open a single changestream per database trigger. I am concerned it is
leading some misunderstandings of the load that Triggers can put on a
customer's cluster(s)

Jira ticket: https://jira.mongodb.org/browse/DOCSP-43465

### Staging Links
<!-- start insert-links -->
<li><a
href=https://deploy-preview-861--app-services.netlify.app/triggers/database-triggers>triggers/database-triggers</a></li>
<!-- end insert-links -->

### Reminder Checklist

Before merging your PR, make sure to check a few things.

- [ ] Did you tag pages appropriately?
  - genre
  - programming_language
  - meta.keywords
  - meta.description
- [ ] Describe your PR's changes in the Release Notes section
- [ ] Create a Jira ticket for related docs-realm work, if any

### Release Notes

<!--
- **Define Data Access Permissions**
- Data Access Role Examples: Update CRUD Permissions example screenshots
and
    copyable JSON
-->

### Review Guidelines


[REVIEWING.md](https://github.com/mongodb/docs-app-services/blob/master/REVIEWING.md)

Author: amalhotra-mdb

source/triggers/database-triggers.txt

@@ -35,9 +35,7 @@ Database triggers use MongoDB :manual:`change streams </changeStreams>`
 to watch for real-time changes in a collection. A change stream is a
 series of :ref:`database events <database-events>` that each
 describe an operation on a document in the collection. Your app opens a
-single change stream for each collection with at least one enabled
-trigger. If multiple triggers are enabled for a collection they all
-share the same change stream.
+new change stream for each database trigger created in a collection. 
 
 .. important:: Change Stream Limitations