Since #3209 (backported in #3327), NewSharedFilesystemV2 can incorrectly choose the v1 API endpoint, which does not work. The problem is that share (the service type for the v1 API) is an acceptable alias for shared-file-system in that PR, instead of only sharev2 (the service type for the v2 API).