build: expose module for external consumption

[lcian]

This way it can be used in other projects.

[seer-by-sentry]

Potential bug: The new sentry_module in build.zig imports the types module but fails to provide its required utils dependency, causing compilation failures for external consumers.

• Description: The new sentry_module is configured to provide the types module to external consumers. However, the types module itself has a dependency on a utils module, as seen in src/types/Event.zig. The build script fails to declare this nested dependency for the sentry_module by omitting a call like types.addImport("utils", sentry_module). This will cause a compilation failure for any external project that consumes the library via the new module system and calls a function like captureError, which relies on the types module.

• Suggested fix: In build.zig, after adding the types import to sentry_module, also add the required utils import for the types module. This can be done by adding types.addImport("utils", sentry_module); to ensure the dependency is resolved during compilation.
  _{severity: 0.8, confidence: 0.95}

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[seer-by-sentry]

Potential bug: The "Git Submodule" integration method in README.md is broken. It bypasses the necessary build script setup, causing a compilation failure due to an unresolved types module import.

• Description: The README.md file presents two methods for integrating the library: Git Submodule and Package Manager. The "Git Submodule" method instructs the user to create a new static library directly from src/root.zig. This approach completely bypasses the project's build.zig file, which is responsible for setting up necessary module dependencies, such as the types module. Since src/root.zig directly imports types, following these instructions will lead to a guaranteed compilation failure because the types module will not be found.

• Suggested fix: The "Git Submodule" instructions in README.md should be removed or corrected. The correct approach must involve using the project's build.zig to properly configure the library and its dependencies, rather than creating a static library from a single source file.
  _{severity: 0.75, confidence: 0.9}

_{Did we get this right? 👍 / 👎 to inform future reviews.}