PIMOB: Java sample app updated for CVV tokenization

[chintan-soni-cko]

Issue

PIMOB-2176

Proposed changes

1. Updated java sample app
2. Added a new button for cvv tokenisation to redirect to the new screen
3. Added a new overloaded method name as provideCvvComponentContent for the merchant who is not using compose in Java or kotlin language

Note: This is a traditional sample app and added minimal UI design just for demonstrating how it will work without compose UI

Tes

java.webm

1. open java sample app
2. click on cvv tokenisation
3. verify amex cvv component and pay button working along with cvv validation working as expected
4. Try to add more customise option for cvv input field
5. Create token with success and failure scenario to test the behaviour

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• Reviewers assigned
• I have performed a self-review of my code and manual testing
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if applicable)

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you choose the solution you did and what alternatives you considered, etc...

[jheng-hao-lin-cko]

Let's add final for all the immutable variables, same for all the other code

Suggested change

	private void createCVVComponentMediator(CVVComponentApi cvvComponentApi) {
	// Create config for CVV component
	CVVComponentConfig visaCVVComponentConfig = new CVVComponentConfig(
	CardScheme.Companion.fromString("unknown"),
	isEnteredCVVValid -> Unit.INSTANCE,
	DefaultCVVInputFieldStyle.INSTANCE.create()
	);
	// Create CVVComponentMediator for CVV component
	CVVComponentMediator defaultCVVComponentMediator = cvvComponentApi.createComponentMediator(visaCVVComponentConfig);
	View defaultCVVComponentView = defaultCVVComponentMediator.provideCvvComponentContent(cvvComponentLinearLayout);
	private void createCVVComponentMediator(CVVComponentApi cvvComponentApi) {
	// Create config for CVV component
	final CVVComponentConfig visaCVVComponentConfig = new CVVComponentConfig(
	CardScheme.Companion.fromString("unknown"),
	isEnteredCVVValid -> Unit.INSTANCE,
	DefaultCVVInputFieldStyle.INSTANCE.create()
	);
	// Create CVVComponentMediator for CVV component
	final CVVComponentMediator defaultCVVComponentMediator = cvvComponentApi.createComponentMediator(visaCVVComponentConfig);
	final View defaultCVVComponentView = defaultCVVComponentMediator.provideCvvComponentContent(cvvComponentLinearLayout);

[jheng-hao-lin-cko]

this can be this?

Suggested change

	override fun provideCvvComponentContent(
	container: View,
	): View = ComposeView(container.context).apply {
	// Dispose of the Composition when the view's LifecycleOwner is destroyed
	setViewCompositionStrategy(ViewCompositionStrategy.DisposeOnViewTreeLifecycleDestroyed)
	setContent { InternalCVVComponent() }
	}
	override fun provideCvvComponentContent(
	container: View,
	): View = provideCvvComponentContent(view, ViewCompositionStrategy.DisposeOnViewTreeLifecycleDestroyed)