chore: remove all logic for older version of plugin (latestVersion)

[alexgerardojacinto]

Source files:

• IONCAMRCameraParameters.kt — removed latestVersion field
• IONCAMRMediaProcessor.kt — processCameraImage: removed onImage and intent parameters, removed var bitmap: Bitmap?, collapsed the if/else to keep only the latestVersion = true branch
• IONCAMRCameraManager.kt — processResultFromCamera: removed onImage parameter, updated the processCameraImage call to match the new signature

Test files:

• TakePictureTests.kt — removed all legacy (latestVersion = false) tests; kept and updated the 4 givenAPI30 tests (removed latestVersion from constructor, removed onImage parameter from
  calls) and added a few new tests that were missing
• ChoosePictureTests.kt — removed latestVersion = false from all IONCAMRCameraParameters constructors
• EditPictureTests.kt — removed the two processResultFromCamera tests that tested the legacy code path (givenTakePictureAllowEditWhenEditProcess*), removed now-unused imports
  (IONCAMRCameraManager, IONCAMRCameraParameters) and the PROCESS_SUCCESS constant

[OS-pedrogustavobilro]

Curious: did you find why some tests are called givenAPI30 and others givenAPI28? Was it just that the latter being called with latestVersion=false? It's kind of weird that they're labelled with the API level when that does not get into account for the actual test.

[alexgerardojacinto]

good question, I don't really know why 😅 New tests were added by Claude and I think it did that because older tests already had that naming pattern?

[OS-pedrogustavobilro]

Yeah, that's fair, I was asking more to know if you knew why they had the API level in the name before. But anyway it's non-blocker, just a curiosity, all good on my end.

[alexgerardojacinto]

@OS-pedrogustavobilro I renamed the tests to remove that

[alexgerardojacinto]

But yeah I think originally we were setting the API level and that's why tests were named like that