The catalog.visibility attribute name may be misleading in the case of shear #381
Description
It is required to assign the visibility attribute to an input catalogue, in order for the maps to acquire the correct fsky value in their metadata. However, because the visibility mask is only relevant to the galaxy positions, a user may neglect to assign the visibility attribute to a shear catalogue, which may lead to unexpected behaviour, eg. in the unmixing. In the case of a shear catalogue, the correct mask to assign in this case is the footprint. Would the most straightforward resolution of this issue be to rename the catalog.visibility attribute to reflect this?