fix: prevent suggestions from activating on password input fields

[Sidd-Panchal]

This PR prevents SuggestPilot from activating on password input fields.

While testing the extension, I noticed that password fields could still pass through the input tracking logic before being filtered later. Since password inputs are sensitive fields, the extension shouldn't attach suggestion logic to them at all.

This change adds a small early check inside setupInputTracking() to immediately return when the focused element is an input[type="password"].

This ensures:

• suggestion listeners are never attached to password inputs
• sensitive fields are ignored earlier in the pipeline
• unnecessary processing is avoided

The change is small and isolated to the content script input tracking logic.

[Shantanugupta43]

Amazing I will try to review and merge prs as soon as possible I have a bit of delay at the moment due to additional responsibilities would review it in around few days