keep the camelCase method to mirror GEE javascript map functions

[12rambau]

I asked this question during the breakout session of Geo4Good, If I understand correctly you are planning on dropping methods that were mirroring GEE javascript ones.

Also I completely understand that respecting the Python convention is making the geempa package more consistent, I wanted to highligh 2 advantages:

• if you are coming from the code editor you know by design that this function is perfectly mimicking the behaviour you would get in the javascript interface
• It gives Python users an insight: this is a earthengine-API call which is very relevant for Commercial users of the lib. That's the reasoning I'm following to refactor geeo_tools.

I think keeping them in painless as it's a 1 liner at the end of the class:

class Map: 
    # ...
    addLayer = self.add_ee_layer

_Originally posted by @12rambau in https://github.com/gee-community/geemap/discussions/1770_

[12rambau]

@giswqs could you assigned the issue to me ? (I won't be coding before monday)