Update the documentation around merge_status attribute
requested to merge 3169-the-merge_status-attribute-can-indicate-the-mr-can-be-merged-when-no-automatic-merge-is into master
What does this MR do and why?
After the introduction of a new attribute 'detailed_merge_status', we should deprecate merge_status as it is already deprecated for graphql, and instead recommend users to not use the 'merge_status' attribute any more, as it does not take into account for some merge checks
Related to #3169 (closed)
Edited by Marc Shaw