clarify r2 lifecycle rule conflict behavior

Author: harshal317

src/content/docs/r2/buckets/object-lifecycles.mdx

@@ -16,7 +16,7 @@ For example, you can create an object lifecycle rule to delete objects after 90
 - An object is no longer billable once it has been deleted.
 - Buckets have a default lifecycle rule to expire multipart uploads seven days after initiation.
 - When an object is transitioned from Standard storage to Infrequent Access storage, a [Class A operation](/r2/pricing/#class-a-operations) is incurred.
-
+- Conflicts between rules are handled by prioritizing the cheapest action. If an object was set to expire on a given day by one rule and set to transition to InfrequentAccess on the same day by another rule the expiration would take precedence. 
 ## Configure lifecycle rules for your bucket
 
 When you create an object lifecycle rule, you can specify which prefix you would like it to apply to.