[Refactor]: Avoid R function names when naming FIMS parameters

[Andrea-Havron-NOAA]

Refactor request

From @kellijohnson-NOAA: In the future it might be good to not name parameters the same name as major functions in R.

example: test-fims-estimation.R

 # Maturity
    maturity <- new(fims$LogisticMaturity)
    maturity$median$value <- om_input$A50.mat
    maturity$median$is_random_effect <- FALSE
    maturity$median$estimated <- FALSE

Expected behavior

Parameter names that do not conflict with R functions within base R or other major R functions.

Current Parameter Name	Proposed Parameter Name
median	x50
recruit_deviations	#402 recruit_multipliers, recruit_scalars

Code of Conduct

• I agree to follow this project's Code of Conduct

[Andrea-Havron-NOAA]

We should go through FIMS and identify other parameter names that conflict with major R functions

[KyleShertzer-NOAA]

Agree in general. Another reason for changing the name of this particular parameter ("median" in the logistic function) is that it's not actually a median, or at least in rare instances would it be the median in either the X or Y direction. This parameter defines the X location of Y=0.5, but 0.5 isn't necessarily the median value. Maybe we call it x50?

[msupernaw]

@KyleShertzer-NOAA I agree, we should be mathematically consistent. In addition, if we aren't going to treat recruitment deviations as deviations, they should also be renamed. I'm sure there are other members throughout the API that need review.

[Andrea-Havron-NOAA]

I started a table in the issue to track parameters that need to be renamed along with any proposed names. We should do thorough search and flag any parameter names that conflict with R or have a name inconsistent with its mathematical meaning.

[k-doering-NOAA]

Work on this was merged in with #503.