Inconsistent naming of BaccoEmu Baryons object

[damonge]

The BaccoemuBaryons object should be called BaryonsBaccoemu to conform with the naming of other baryonic effect objects (e.g. BaryonsSchneider15 or BaryonsVanDaalen19).

Unfortunately this slipped through after tagging v3, and changing it would break the API. Thoughts?

[damonge]

The solution should be to rename a BaccoemuBaryons into BaryonsBaccoemu, and create a class called BaccoemuBaryons that inherits from it and simply throws a deprecation warning if initialised.

[nikosarcevic]

The solution should be to rename a BaccoemuBaryons into BaryonsBaccoemu, and create a class called BaccoemuBaryons that inherits from it and simply throws a deprecation warning if initialised.

I would suggest naming it "BaryonsArico20" to keep consistent with other modules.

[zdu863]

The solution should be to rename a BaccoemuBaryons into BaryonsBaccoemu, and create a class called BaccoemuBaryons that inherits from it and simply throws a deprecation warning if initialised.

Do we need to create separate unit tests for the deprecated class?