Detect functions that never return (and @noreturn annotation)

Some functions, such as error, never return control to the caller. This can be used to prove that a value is not nil, for example:

function my_function(input)
  local value = input.value or error('Missing value')
  -- The following line would currently raise a "Needs nil check" warning
  -- However, if it was nil at runtime, an error would have been raised and it would never get this far.
  return value:sub(1, 3)
end

It's not just error that can cause this, however. A custom function could be written that never returns as well (the most obvious way is that the function unconditionally calls error, but there may be other ways involving coroutines or functions implemented in C). A @noreturn annotation could be used to indicate this, similar to @nodiscard.

Aucun fichier ni test n’est indiqué dans l’issue. Commencez par suivre l’avertissement de vérification de nil et la gestion existante de l’annotation @nodiscard, puis déterminez comment devraient être représentés les built-ins qui ne retournent pas, les fonctions personnalisées et @noreturn ; le travail est terminé lorsque l’exemple n’émet plus d’avertissement et que le comportement de l’annotation est couvert.