Backport (1.x): Add limits to #log_deprecation

[delner]

What does this PR do?

Backports #3675 to 1.x-stable. I intend to rebase #3647 on top of it to leverage the limit feature.

[datadog-datadog-staging-us1-all]

Static Analysis Violation (ruby-best-practices/concat-strings)

⚪ Notice - Best Practices - View in Datadog

Suggested change

	message += ' This will be enforced in the next major release.' if disallowed_next_major
	message << ' This will be enforced in the next major release.' if disallowed_next_major

Avoid appending to string using += (read more)

The rule to avoid slow string concatenation in Ruby is essential for writing efficient and fast-performing code. String concatenation using the += operator is slower because it creates a new string object every time it's used. This can lead to performance issues, especially in loops or large programs where numerous string concatenations might be happening.

Instead, the << operator, also known as the append operator, should be used for string concatenation in Ruby. The << operator modifies the original string, avoiding the creation of multiple unnecessary string objects. This results in faster execution time and lower memory usage, which is especially beneficial in larger applications or systems with limited resources.

Therefore, good coding practice in Ruby suggests using << for string concatenation instead of +=. For instance, output << "<p>#{text}</p>" is more efficient than output += "<p>#{text}</p>". Following this rule will help you write cleaner, faster, and more resource-efficient Ruby code.

Leave feedback in #static-analysis