2.15.0 changed the result of serialization of functions returning boolean

[PoisonedYouth]

Describe the bug
The result in serialization of a function returning a boolean is changed from version 2.14.2 and 2.15.0.

To Reproduce
2.14.2

interface TestInterface{
        fun isValid(): Boolean
    }

    class TestClass: TestInterface{
        override fun isValid(): Boolean {
            return true
        }
    }

    @Test
    fun `serialize`(){
        val test = TestClass()

        val actual = jacksonObjectMapper().writeValueAsString(test)

        assertThat(actual).isEqualTo("{\"valid\":true}")
    }

2.15.0

interface TestInterface{
        fun isValid(): Boolean
    }

    class TestClass: TestInterface{
        override fun isValid(): Boolean {
            return true
        }
    }

    @Test
    fun `serialize`(){
        val test = TestClass()

        val actual = jacksonObjectMapper().writeValueAsString(test)

        assertThat(actual).isEqualTo("{\"isValid\":true}")
    }

Expected behavior
The serialization of functions does not change.

Versions
Kotlin: 1.8.20
Jackson-module-kotlin: 2.15.2
Jackson-databind: SpringBoot: 3.0.6 (brings jackson-databind 2.14.2)

Additional context
Add any other context about the problem here.

[k163377]

This is a destructive change caused by #641.

There were certainly undesirable aspects to this change.
However, I believe the overall benefit would be greater if this behavior were left as is.

The reasons are as follows

• Difficulty in fixing this problem without causing recurrence of problems like Regression on data binding in 2.11.0 with specific field naming #340 .
  • Need to determine if java-getter is a property or getter-like in Kotlin.
    • Complex processing is required to achieve this, which also increases the load on serialization.
• Defining it as a property instead of getter-like avoids the problem.

Unless we get a lot of requests or find a better fix, I would like to hold off on fixing this issue.

[PoisonedYouth]

For me it breaks the serialization of one of my projects. I didn't expect the change according to the release notes / migration guide. Or did I overlook something?

Generally I don't have problems with this change, it's just it's unexpected behavior for me.

[k163377]

I didn't expect the change according to the release notes / migration guide.

Yes, we did not detect that such regression was occurring.
A reference to this issue will be added in the future.

[PoisonedYouth]

Thank you very much.

[pjfanning]

@k163377 can this be closed due to https://github.com/FasterXML/jackson-module-kotlin/blob/2.16/release-notes/VERSION-2.x#L25-L27 ?