feat: @ComponentScan glob support

[OffRange]

Summary

This PR enhances the @ComponentScan annotation in Koin Annotations to support glob patterns. Currently, @ComponentScan only allows specifying a single, exact package name per Koin module. With this change, developers can use wildcards (* and **) to scan multiple packages or subpackages in a more flexible and concise way.

Motivation

In modern, modular JVM applications, components (like services, repositories, or utilities) are often spread across multiple subpackages. The current @ComponentScan requires developers to either:

1. Create a Koin module for each subpackage, leading to module proliferation.
2. Place all components in a single package, which can become unwieldy.

By supporting glob patterns, we allow developers to organize their code more naturally without compromising on Koin's autowiring capabilities.

Implementation

1. Added GlobToRegex.kt utility:

   • Converts glob patterns to regular expressions.
   • Supports * (single-level) and ** (multi-level) wildcards.
   • Case-sensitive by default, as package names in JVM are case-sensitive.

2. Modified KoinMetaDataScanner and KoinMetaData:

   • Now uses custom extension function to interact with the GlobToRegex utility

3. Tests

   • Still passes

Examples

Before:

@ComponentScan("com.app.service")
class ServiceModule
@ComponentScan("com.app.service.user")
class UserServiceModule
@ComponentScan("com.app.service.order")
class OrderServiceModule

After:

@ComponentScan("com.app.service.**")
class ServiceModule

However we can still use:

@ComponentScan("com.app.core")
class CoreModule

[arnaudgiuliani]

Hello,

great addition. Could you add some local unit tests to help be sure we cover those regex?

Thanks 🙏

[OffRange]

Hello,

great addition. Could you add some local unit tests to help be sure we cover those regex?

Thanks 🙏

Of course, since all tests are located in modules within the examples module, I assume my tests should be placed there as well. Do you have any preferences regarding a specific module? Alternatively, would you prefer that I create a new module within examples for the regex testing, or should I create a new test source set for the koin-ksp-compiler module within the projects module?