FormInputField::Integer doesn't handle 0n prefix

Version and Platform (required):

• Binary Ninja Version: 4.1.5246-dev
• OS: macOS
• OS Version: 14
• CPU Architecture: M1

Bug Description:
The FormInputField APi for Integer fields doesn't respect the 0n1234 convention binja generally uses for numbers, nor does it use hex-by-default conventions either. We should make it match the integer parsing behavior seen elsewhere in the app.

Steps To Reproduce:

1. Run this python:

fi = IntegerField('int')
get_form_input([fi], 'a')
fi.result

2. Try to type 0n1234
3. Observe error box
4. Type 1234
5. Observe result is decimal 1234 and not 0x1234

Expected Behavior:
I expected integer form inputs to match the rest of the product

Additional Information:
Likely in mainwindow's interaction handler

Start at the mainwindow interaction handler mentioned in the report and trace how IntegerField input is parsed. Reproduce the issue with the supplied Python snippet, then verify that 0n1234 is accepted and that an unprefixed 1234 follows the product's hex-by-default convention.