ID 225771 - File Path folders with a '#' symbol are replaced with the frame number

Problem summary
When reading a file path into a 'File_Knob' which contains a '#' symbol somewhere within its folder path, Nuke fails to load the file. 

Nuke attempts to convert the '#' symbol into the scene's frame number as displayed in the example below:

Example Path:  test/testing_#/testFile.png

Nuke's path resolution:  test/testing_1/testFile.png

Customer reported version
nuke.10.5v3

Steps to reproduce

1) Create a new folder with a '#' (For example 'Test_#_Folder')

2) Add an image file to the folder

3) Open Nuke

4) Create a Read node, link the file knob to the image

Result: The read node will display the following error 'Read Error: No such file or directory'

Workaround
This can be worked around by adding a '%' character in front of the '#' in the path.

Example path:  test/testing_%#/testFile.png, 

Nuke's path resolution: test/testing_%#/testFile.png, 

Reproduced by support

This bug has been reproduced in:
Nuke11.0v2 - Windows 7 - Mac10.12 - CentOS6.9
Nuke11.0v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke10.5v6 - Windows 7 - Mac10.12 - CentOS6.9
Nuke10.5v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke10.0v6 - Windows 7 - Mac10.12 - CentOS6.9
Nuke10.0v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke9.0v9 - Windows 7 - Mac10.12 - CentOS6.9
Nuke9.0v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke8.0v7 - Windows 7 - Mac10.12 - CentOS6.9
Nuke8.0v6 - Windows 7 - Mac10.12 - CentOS6.9
Nuke8.0v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke7.0v10 - Windows 7 - Mac10.12 - CentOS6.9

Earliest version tested
- This issue appears to be in all versions of the product

Expected behaviour
The file_knob within Nuke should only replace a '#' symbol if the symbol is within an image file.

Actual behaviour
The '#' symbol is replaced with the frame number anywhere in the file path.