Requireopt

[noresources]

What does this PR do?

Adds new API requireopt() to require a module without throwing an error

How does this PR change Premake's behavior?

Also adds a third argument silent to the existing require() (default: false)

Anything else we should know?

Use case: Have a way to handle optional modules.
Example

local doxygen = requireopt("doxygen")
if doxygen then
  doxyfile {
    project_name = "..."
  }
end

Did you check all the boxes?

• Focus on a single fix or feature; remove any unrelated formatting or code changes
• Add unit tests showing fix or feature works; all tests pass
• Mention any related issues (put closes #XXXX in comment to auto-close issue when PR is merged)
• Follow our coding conventions
• Minimize the number of commits
• Align documentation to your changes

[nickclark2016]

This should probably be named "test_globals.lua" to match the name of the file we are testing.

[noresources]

File was named based on existing test named "tests/base/test_module_loader.lua"

[nickclark2016]

Documentation? I'm not completely sold on "requireopt", as that feels like an oxymoron to me. What about "tryrequire"?

[noresources]

I agree. It was named requireopt in an effort to follow existing naming convention, based on the existing dofilepot.
IMO, both of them should be renamed try<thing>