consider container type in PIResponse

[nilsbehlen]

No description provided.

[Copilot]

Pull Request Overview

This PR adds support for smartphone container types in PIResponse, treating them as equivalent to push tokens for authentication purposes.

• Introduces CONTAINER_TYPE_SMARTPHONE constant to handle smartphone container types
• Updates all push-related methods to also consider smartphone containers as push tokens
• Refactors duplicate type checking logic into a reusable helper method

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
PIConstants.java	Adds CONTAINER_TYPE_SMARTPHONE constant and updates comment to reflect container types
PIResponse.java	Updates push token detection to include smartphone containers and refactors type checking logic

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The removal of passkeyMessage field appears unrelated to the PR's purpose of considering container types. This change should be in a separate commit or explained in the PR description to maintain clear change separation.

[Copilot]

[nitpick] Consider maintaining alphabetical order in static imports for better readability and consistency.

Suggested change

	import static org.privacyidea.PIConstants.CONTAINER_TYPE_SMARTPHONE;
	import static org.privacyidea.PIConstants.TOKEN_TYPE_PUSH;
	import static org.privacyidea.PIConstants.TOKEN_TYPE_WEBAUTHN;
	import static org.privacyidea.PIConstants.TOKEN_TYPE_PUSH;
	import static org.privacyidea.PIConstants.TOKEN_TYPE_WEBAUTHN;
	import static org.privacyidea.PIConstants.CONTAINER_TYPE_SMARTPHONE;