FileInputPane producing inaccurate file warnings

[capricornunicorn123]

Prerequisites

• Put an X between the brackets on this line if you have done all of
  the following:

  • Running the latest version of Constellation

  • Attached the Support Package via Help >
    Support Package

  • Checked the FAQs:
    https://github.com/constellation-app/constellation/wiki/FAQ

  • Checked that your issue isn’t already filed:
    https://github.com/constellation-app/constellation/issues

  • Checked that there is not already a module that provides the
    described functionality:
    https://github.com/constellation-app/constellation/wiki/Catalogue-of-Repositories

Description

Recent enhancements have been made to the file chooser dialog that is used when saving and opening files in Constellation.
There are three issues that occur during file import and export with FileInputPane's.
1 - The file dialog that is produced when a file is saved using a PluginParameter FileInputPane incorrectly checks for a .svg version of a file not a duplicate of the current type.
2 - The file dialog that is produced when opening a file using a PluginParameter FileInputPane incorrectly warns user that the file already exists.
3 - The file dialog appears on (presumably) the primary monitor. Note the monitor currently hosting the application.
4 - When exporting a file to SVG, if the file already exists, the user does not get a file override warning that already exists.

Steps to Reproduce

1 - File Save
a) Open a graph
b) Export the graph to an SVG
c) export the graph to a KML
d) Save the KML in the same location as the exported SVG
e) Note the warning dialog

2 - File Open
a) Open the Data Access View
b) Navigate to the Test Parameters Plugin
c) Select Open File parameter
d) Select a text file.
e) Note the warning dialog.

3 - Monitor issue
a) Trigger a file overwrite dialog with the application on monitor 1.
a) Trigger a file overwrite dialog with the application on monitor 2.
c) Trigger a file overwrite dialog with the application on monitor 3.
d) Note the location of the popup in these three instances.

Expected Behaviour:
Importing Files should never warn users that a file is going to be overwritten. Maybe a warning that a file is already open could be useful.

Exporting files should warn users that a file is going to be overwritten only if the file exits. The existence of should check the file name, the path to the file and the file extension.

Popups should always appear on the same monitor as the application (especially when the popup is modal (block application interaction)).

Reproduces how often:
100%

Additional Information

@Quasar985 may have additional context around this issue.