Makes botany chem production scaling have diminishing returns

[M-Earthfire]

[Balance][Hydroponics][Input wanted]

About the PR

This PR introduces proc/HYPchem_scaling and proc/HYPfull_potency_calculation and uses them to add diminishing returns to all chem production scaling of botany.

The graphs are given here: https://www.desmos.com/calculator/gy7tn43s6b

Before reaching 50 potency, produce will stlightly give more chemicals. After reaching 50 potency, the effectiveness of potency drastically decreases, with reaching 80u of chems as 100 potency, down from 100. With potency reaching infinity, the amount of added chemicals with cap out at 200.

Why's this needed?

Linear scaling of chems within botany meant that balancing botany chem production is neigh impossible and people were able to create ridicilous amount of chemicals within single items very quickly. Example of these are 300u+ morphine peanuts or quick 7x7 fireball seethers.

These changes will keep the numbers in a reasonable range and will slow down the more ridicilous plants.

The changes proposed here will affect beginners and "normal" botany production not at all or only in a minor way, since diminishing returns start at 50 potency and only drastrically ramp up beyond 100 potency.

With this changes, balancing plants for lower statistics should become easier and it should create more design space when designing new botany chemicals or plants.

Changelog

(u)Lord_Earthfire
(*)Chemicals produced by plants show diminishing returns with increasing potency. See the minor logs for more information.
(+)Diminishing returns for botany scaling start at 50 potency, with 80% effectivity at 100 potency.

[github-actions]

Created discussion thread: https://forum.ss13.co/showthread.php?tid=22277

[NibChocolateeny]

i think it is ok - but it may be very bad for omeaga weed (but I know it is joke plant)

testmerge first?

[github-actions]

This PR has been inactive for two weeks, and has been automatically marked as stale. This means it is at risk of being auto closed in another week. Please address any outstanding review items and ensure your PR is finished. If you are auto-staled anyway, ask developers if your PR will be merged. Once you have done any of the previous actions then you should request a developer remove the stale label on your PR, to reset the stale timer. If you feel no developer will respond in that time, you may wish to close this PR youself, while you seek developer comment, as you will then be able to reopen the PR yourself.