bsp: Update BSPs for using button v4 (only LVGL port changes)

[espzav]

ESP-BSP Pull Request checklist

• Version of modified component bumped
• CI passing

Change description

• Updated LVGL port for using it with button component v4

Closes #494

[github-actions]

Test Results

 17 files  17 suites   5m 52s ⏱️
 68 tests 24 ✅  44 💤 0 ❌
408 runs  24 ✅ 384 💤 0 ❌

Results for commit 96e5b85.

♻️ This comment has been updated with latest results.

[espzav]

@tore-espressif PTAL

[tore-espressif]

@espzav esp_lvgl_port LGTM.

I don't have any of these boards now to test...

Strictly speaking, bump of major version of public component is a breaking change -> we should bump major versions of the BSPs too...
However, looking at the button v4 changes, there are only 2:

• Button creation -> this is handled by BSP
• Register/unregistering of button callback -> this will require users to change their code, if they use these functions

[espzav]

However, looking at the button v4 changes, there are only 2:

I am not sure, if there are real breaking changes:

1. When you are using button v3 with LVGL port --> No breaking changes
2. When you change from v3 to v4 button with LVGL port --> You must make changes
3. In BSPs, there is everything handled inside or in examples --> No breaking changes

[espzav]

And when I am thinking about it, there can be solution for use both version of button in BSPs too. I am not suer, if we want it (add more ifdefs)

[tore-espressif]

And when I am thinking about it, there can be solution for use both version of button in BSPs too. I am not suer, if we want it (add more ifdefs)

I'd prefer supporting only one (the latest) version

[espzav]

I'd prefer supporting only one (the latest) version

OK, should I increase major version of affected BSPs?