Simplify the usage of the Framework

[Mom0aut]

Currently there is a lot of configuration needed to get the DynamicRelations working (DrmConfig,RealtionType)
It should be possible to streamline the usage of the framework to a simpler process.
Any suggestions are welcome

[joonseolee]

@Mom0aut

Hi! While integrating DynamicRelations, I noticed a couple of areas where we could streamline the developer experience.

Simplify @Relation usage

Right now, Relation requires repeating the class name, which feels redundant.
We could infer the declaring type via reflection so that users can write the following:

@Relation
public class Person {}

Rationale: avoid repeating the class name and let the framework detect the type automatically.
Benefits: less boilerplate, fewer typos, improved readability.

Improve DrmConfig registration (@EnableDynamicRelation)

Currently, users need to import DrmConfig manually via @import, which is less ergonomic.
Providing an @EnableDynamicRelation annotation—similar to other Spring-based libraries—would make the setup more intuitive.

// AS-IS
@Import(DrmConfig.class)
public class SpringBootStartApplication {}

// TO-BE
@EnableDynamicRelation
public class SpringBootStartApplication {}

Rationale: expose a clear opt-in entry point for configuration.
Benefits: better UX and consistency with common Spring auto-configuration patterns

[Mom0aut]

Thanks for your suggestions, i rly like them 😄

[joonseolee]

@Mom0aut

I have posted a PR.
Can you check it?

[Mom0aut]

merged with #46