puppet-strings insists on redundant return value for puppet functions

[smortex]

Describe the Bug

When generating the documentation of a Puppet function, puppet-strings wants to see a @return tag in the comments, while the code already include the returned type.

Expected Behavior

puppet-strings should not want a @return tag.

Steps to Reproduce

Generate the documentation of a function (example taken from stdlib):

# @summary function to cast ensure parameter to resource specific value
function stdlib::ensure(
  Variant[Boolean, Enum['present', 'absent']] $ensure,
  Enum['directory', 'link', 'mounted', 'service', 'file', 'package'] $resource,
) >> String {
  # [...]
}

Note the >> String that tells what the function returns.

Environment

• Version : 2.9.0
• Platform : Any

Additional Context

Suggested by @ekohl in puppetlabs/puppetlabs-stdlib#1239 (comment)

[greatflyingsteve]

Currently, the generated Markdown documentation will contain the return type whether or not a @return tag exists; however, Strings will still issue a warning about the missing tag. It should always be possible to include a tag, and that's of course what's recommended in the style guide, but if your type names are sufficiently descriptive, just being forced to type in a @return to shut Strings up feels pretty superfluous, especially for very simple returns.

[ekohl]

puppet-strings should not want a @return tag.

I'd narrow this down to "if a data type can be determined"