Fix for masking when input value is established on component mount

[mattheyan]

Description

On the entries page, if you have a form with formatted text fields (ex: phone, zip code, etc.) and you switch from editing an existing entry (with a value in that field) to creating a new entry, the form for the new entry will appear to have the value from the existing entry that you were editing.

When the mask directive's bind method is called, it calls updateValue which mask's the input's value and updates it and raises an input event if needed. This typically isn't relevant to us since we store formatted values, but it also has the side-effect of setting the oldValue in the config. A subsequent update call will call updateValue, which checks oldValue to determine if the value has changed. If oldValue was never established, at that point it will think the value is different and as a result mask the value and raise an input event. It appears this happens because the element input component doesn't set the value via a binding, but instead does it programmatically in the mounted hook. I believe this is what causes both the input not having a value in bind, as well as the value being stale when update is called.

Checklist

• Tests
• Documentation
• Used commitizen and followed Conventional Commits
• Commit footer references issue num. If applicable.