Make NFSRODS work when restarting NFSRODS without remounting

[ganning127]

changes made

• removed all usage of getAndIncrementFileId(), so we are no longer using an incremental counter as the inode numbers'
• all inode numbers are based off of data_id now
• if NFSRODS is restarted, both the inodeToPath_ and pathToInode_ hashmaps will be cleared out. thus, getPath() will return null. now, if getPath() returns null, we will ask GenQuery for where we are within the filesystem

[korydraughn]

Consider squashing now so no one is confused by the didn't mean to delete code commit.

[ganning127]

squashed!

[ganning127]

the small timeout issue right now, is that if you run docker restart nfsrods, and then run a command like ls immediately after (like without giving the NFSRODS instance a second or so), NFSRODS will output a short error message, before coming alive again.

$ docker restart nfsrods
nfsrods
$ ls
nfs server localhost:/: not responding
nfs server localhost:/: is alive again
anotherFolder                            dave.txt                                 lightsssss.txt
asdfasdfasd.txt                          daveFolder                               macBookPro.txt
aslkdfjalksjfasdjfakasfljkasdfjlkadf.txt davvvvvveee.txt                          newBrah.txt
bar.txt                                  eagle.txt                                newFileGanning.txt
booobooo.tasdfas                         foo.txt                                  stuffs
coocoo.txt                               grrr.txt                                 testFolder
daaaaa.txt                               laksdfljkas.txt

[ganning127]

however, viewing, listing, and editing files all work as normal now after doing restart without re-mounting

[trel]

oh... this is very cool.

that error message is the 'client side' printing that out - and it's due to the NFSRODS server not responding fast enough. not sure there's anything we can do about that except eventually work to optimize startup time (a bit out of our control as we're just providing the virtual filesystem backend to the NFS4J server framework).

[trel]

the next pass through the code, please remove all the deadcode and consider some comments for 'why' you're adding the things you've added. please send flare for when you want eyeballs/comments on the code itself.

good stuff.

[trel]

looking very good - need some @korydraughn eyeballs before squashing.

[korydraughn]

Will look as soon as I can.

[ganning127]

Just leaving this here for reference. We're having some inconsistencies with some tests failing on Linux but not on macOS. Specific details are in this new issue: #187