Add MvcMethod object for setMvcMethod and getMvcMethod.

[agentgt]

Currently setMvcMethod and getMvcMethod are a java.lang.reflect.Method.

The original impetus for set/getMvcMethod was for metrics and the actual java.lang.reflect.Method is not even needed but rather method name and signature.

I propose based on this comment: #3529 (comment)

That we replace get/setMvcMethod(io.jooby.MvcMethod method).

MvcMethod type would have enough metadata so that one could get the java.lang.reflect.Method dynamically if desired.

This will avoid reflective lookup during registration regardless of whether nor setMvcMethod is enabled or not.

I can do a PR for this for 3.4.0 depending on timeline of 3.4.0

[agentgt]

The other advantage to this is if one actually did want to call the method they can use the more modern and in theory faster MethodLookup API.

[jknack]

We can probably add it, but either this way or just enabling the option in jooby-apt will require you to update all your projects, no?

[agentgt]

Correct.

The code change is minor as that is one place but the compiler flag is not because of Maven limitations.

I’m proposing it because it is the right thing to do. We should not kick off reflection on initialization.

[jknack]

Ok, send a PR so we can release 3.4.0 with the change

[agentgt]

@jknack This probably a silly question but I assume we are still targeting jDK 17 for 3.4.0 correct? I'm fairly sure but just want to check.

[jknack]

absolutely. jooby 4.0 will be 21

[jknack]

The apt option will be off by default in next major release: 4.0 regardless of how we model this object

[agentgt]

Sorry @jknack I ran out of time. Can we shoot to add this for 3.5.0?

[agentgt]

Never mind I see you already put it in. Thanks for implementing and I'm sorry I wasn't much help on it. I had some other work and I was trying to make a window for this and #3498 so that I was full jooby focus.

Thanks for putting it in!