Adding Password Component

[shravani-0811]

Description

Adds a new **Adaptive Form Password Input ** core component: a masked <input type="password"> field with an optional show/hide visibility toggle button.

Related Issue

Motivation and Context

Adaptive Forms didn't have a first-class password field: authors had to repurpose Text Input, which offers no masking, no visibility toggle, and no autofill-attribute control suited to credentials. This adds that as a proper, accessible core component while closing off the plaintext-exposure trap that comes from naively inheriting Text Input's "default value" behavior for a password-typed field.

How Has This Been Tested?

• Java unit tests (TextInputImplTest): field type resolution (fieldType=password → getFieldType()/getExportedType()), isShowHidePasswordEnabled() default-true and author-disabled cases, and .model.json export shape via testJSONExport.
• Cypress authoring tests (passwordinput.authoring.cy.js): dropping the component into a form container / responsive grid via the editor sidebar, and opening its edit dialog.
• Cypress runtime tests (passwordinput.runtime.cy.js): model/view initialization, masked-by-default rendering, clicking the eye icon reveals plaintext and toggles aria-pressed/aria-label (and back), toggle button absent when showHidePassword is disabled, value submits correctly regardless of toggle state, minLength/mandatory validation messages, description/tooltip toggling, and aria-disabled absence when disabled.
• Manual verification: deployed to a local AEM SDK author instance; confirmed the component appears in the standard Adaptive Form component sidebar and renders/toggles correctly (masked ↔ plaintext, aria-pressed flips) in the disabled/preview rendering path.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes and the overall coverage did not decrease.
• All unit tests pass on CircleCi.
• I ran all tests locally and they pass.

[adobe-bot]

Accessibility Violations Found

Id	Impact
aria-required-attr	critical
empty-heading	minor
label-title-only	serious
target-size	serious

[adobe-bot]

Accessibility Violations Found

Id	Impact
aria-required-attr	critical
empty-heading	minor
label-title-only	serious
target-size	serious