Improve speed in SurfaceH5 methods

Currently in SurfaceH5 some methods are loading from H5 the Surface triangles/vertices multiple times.

First we should check where these methods are used and decide if their position is correct on the SurfaceH5 module, or should be moved (e.g. in some Displayer inherited class).

The decide on a caching mechanism, to ensure triangles and vertices are read only if needed and only once.