fix: Add PlanningPinToIndex to Python

[Christopher-Chianelli]

JPyInterpreter

• Allow annotations to specify a type to override the generated getter return type. When a type is specified, it goes through the generic PythonLikeObject to Java Object convertor.

Python

• Add PlanningPinToIndex
• Make PlanningPin use the new JPyInterpreter mechanism to remove code that converts a PlanningPin to Pinning filter

Build

• Fix Python 3.12 environment name in tox.ini

[Christopher-Chianelli]

Fixes #1190

[triceo]

The field should not support null values - there is no reason for why the field should have a reference type. If the Javadoc says it, let's fix the Javadoc.

[Christopher-Chianelli]

Counterpoint:

• @PlanningPin allows null/using Boolean (i.e. not allowing Integer will be inconsistent)
• There is no performance benefit from not allowing Integer, since the field is automatically boxed by MemberAccessor
• Users might have restrictions that prevent them from using primitive types.

[triceo]

• @PlanningPin allows null/using Boolean (i.e. not allowing Integer will be inconsistent)

You could also say that we shouldn't repeat mistakes of the past.

• There is no performance benefit from not allowing Integer, since the field is automatically boxed by MemberAccessor

I agree. Performance is irrelevant here. I simply do not see the point of allowing this field to have a third state (null).

• Users might have restrictions that prevent them from using primitive types.

This particular type has not supported null since the start, and there were zero complaints. That tells me null is not necessary there. (Besides the fact that there is no practical use for putting null here - zero is the perfect default for this use case.)

We can add it if we ever see the need. But I am not a fan of adding options that nobody is calling for.

[sonarqubecloud]

Quality Gate failed

Failed conditions
65.6% Coverage on New Code (required ≥ 70%)

See analysis details on SonarCloud