Remove glfw from the engine builds

[Jhonnyg]

GLFW is no longer being built as part of our main engine build. Instead, the current GLFW version (modified 2.7) is now begin built and distributed as an external package. We have also removed GLFW from our SDK, which means that some extensions might potentially break. This is considered a bugfix instead of a breaking change, since the headers should never have been part of the SDK from the first place.

This is the second part of our ongoing task (#7970) of migrating the current GLFW version to the latest stable official release, as well as separating all non-desktop platforms our of the GLFW infrastructure.

PR checklist

• Code
  • Add engine and/or editor unit tests.
  • New and changed code follows the overall code style of existing code
  • Add comments where needed
• Documentation
  • Make sure that API documentation is updated in code comments
  • Make sure that manuals are updated (in github.com/defold/doc)
• Prepare pull request and affected issue for automatic release notes generator
  • Pull request - Write a message that explains what this pull request does. What was the problem? How was it solved? What are the changes to APIs or the new APIs introduced? This message will be used in the generated release notes. Make sure it is well written and understandable for a user of Defold.
  • Pull request - Write a pull request title that in a sentence summarises what the pull request does. Do not include "Issue-1234 ..." in the title. This text will be used in the generated release notes.
  • Pull request - Link the pull request to the issue(s) it is closing. Use on of the approved closing keywords.
  • Affected issue - Assign the issue to a project. Do not assign the pull request to a project if there is an issue which the pull request closes.
  • Affected issue - Assign the "breaking change" label to the issue if introducing a breaking change.
  • Affected issue - Assign the "skip release notes" is the issue should not be included in the generated release notes.

---

Example of a well written PR description:

1. Start with the user facing changes. This will end up in the release notes.
2. Add one of the GitHub approved closing keywords
3. Optionally also add the technical changes made. This is information that might help the reviewer. It will not show up in the release notes. Technical changes are identified by a line starting with one of these:
   1. ### Technical changes
   2. Technical changes:
   3. Technical notes:

There was a anomaly in the carbon chroniton propeller, introduced in version 8.10.2. This fix will make sure to reset the phaser collector on application startup.

Fixes #1234

### Technical changes
* Pay special attention to line 23 of phaser_collector.clj as it contains some interesting optimizations
* The propeller code was not taking into account a negative phase.

[Jhonnyg]

there might be better ways to package this, but the old / current way of packaging isn't working with latest waf afaik, so for now this works "good enough"

[JCash]

👍

[JCash]

We should also consider removing "--with-vulkan" from the build scripts, and instead add "--with-opengl"