Pass verbose argument to insight::get_parameters() calls

[Copilot]

Description

The verbose argument was not being passed to insight::get_parameters() calls, causing unwanted warnings to propagate to downstream packages like {statsExpressions}.

Proposed Changes

Added verbose = verbose parameter to all insight::get_parameters() calls within functions that accept a verbose argument:

• .effectsize_contingencyTableBF() - line 99
• .effectsize_correlationBF() - line 172
• .effectsize_proportionBF() - line 185
• .data_from_formula() - line 42

This ensures warnings are properly suppressed when users set verbose = FALSE.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Consistently passing verbose to the underlying method</issue_title>
<issue_description>This is just one example, but I think there are a few others in the codebase:

effectsize/R/effectsize.BFBayesFactor.R

Lines 171 to 172 in 64afba0

	.effectsize_correlationBF <- function(model, type = NULL, verbose = TRUE) {
	rho <- insight::get_parameters(model)[["rho"]]

Here, verbose argument should be passed to insight::get_parameters(), but it isn't.

This discrepancy is leading to some unnecessary warning messages bubbling up in downstream packages, like {statsExpressions}.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Consistently passing verbose to the underlying method #688

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[IndrajeetPatil]

Failing workflows unrelated to the changes in the current PR. So ignoring them before merging.