Review function names and behavior in this package

[yeesian]

(The last time I went through such an exercise was in yeesian/GDALUtils.jl#2 (comment).)

The considerations I can think of are:

1. it will not always be 1:1 in behavior with the correspondent GDAL C functions (otherwise there'll be surprises like write geopackage #263 (comment))
2. it should be sufficiently inferable from the corresponding GDAL C function names for discoverability (c.f.rename layerdefn to getlayerdefn or provide alias #312)
3. it should be consistent across types (e.g. "create", "write" or "read" etc across different GDAL object types)
4. they should be documented in https://yeesian.com/ArchGDAL.jl/stable/considerations/#Design-Considerations