Better compatibility with remote Stash site

Thanks JohnnyBeGood for providing a test site so I can troubleshoot the problem of remote mode.
Now it should work better with the remote Stash machine, hopefully.

Better play button

Now the play button can play current browser tab's movie/scene/images/gallery instead of choosing individually. Also you can use Alt-P to as the play shortcut key.

Small fixes

This is just a release with small fixes.

• Settings improvements including added DeoVR player as a media player.
• Better way to test Stash URL when loading.

Enable Remote mode vs default Local mode.

Stash Helper was originally designed to be running like NZBget, which runs Stash in local and access all features in local. It works great for me. I have some nice features, like Scraper Manager, which only possible when running locally.
However, the more I get in touch with the guys in Stash, the more I realize that most of them are browsing Stash remotely. My program was not designed that way, therefore lots of useful features in Stash Helper are not available for them. So this weekend I decided to work it out.
The result is the brand new v2.3.0. Lots of internal mechanism have changed, maybe it's more buggy now, but at least you can set Stash Helper to "remote" mode vs the original "local" mode. Finally Stash Helper can help you with your Stash running in a docker or NAS.

Features are still working in "Remote" mode:

• Bookmarks
• Play current scene/movie. Note: In remote mode, scenes will be sent as "online streams" to the media player. PotPlayer and VLC can handle them.
• Play current Gallery/Images
• Scan new files
• Create Movie(s) from Scene(s)
• CSS Magic
• Playlist Add/Clear/Manage/Send to media player

Features not available in "Remote" mode:

• Scraper manager
• Open media folder
• Automatic closing of Stash console.

Overall, I am glad that I successfully kept most the features available in remote mode. The coding is surprisingly not as much as I had expected. Maybe I am just getting better at this. 😄

Browser Profile: Private or Default ?

I am very glad to be able to implement a new profile setting for the web browsers: Private or Default.

• Private profile will run Stash with a temporary profile. Your browsing history will not show anything about Stash. It works best for computers in a company which you really don't want anyone to see what you have been browsing. The downside is that , since it's always a temporary profile, each time it will forget all the settings or bookmarks you have changed.
• Default profile will run Stash with the default user profile. You can save bookmarks and settings, add your own browser add-ons, and it will remembers it next time you launch the browser.
  It's up to you to decide which profile you want to use. Of course, the default setting is "Private Profile".
  
  
  

Small fixes

• Scraper manager had small problem at the end of the file. Fixed.
• Added a couple of CSS snippets.
• Force update the webdriver if a browser failed to start.

Better Gallery

Now all the gallery files are local. Viewing galleries doesn't require you to connect to Internet any more. It also makes loading a gallery much faster.

Better folder Setting handling.

I didn't realize that some people will choose %userprofile%/.stash as the Stash data folder. Silly me.
So this version improves upon it by allowing both:

• If you use local working folder, Stash Helper will work just like before.
• If you use .stash as the data folder, Stash Helper now has no errors in getting scraper lists.

Well, I am sure there must be other places that will have trouble with different data folders. So if you see such an error, please create an issue and let me know. Thank you!

Better Scraper Manager, more fix with gallery

• Tested with Stash v0.12 upgrade. Seems the auto-update is working for me.
• Now the scraper manager will show green color for the scrapers that are installed. Less confusion.
• A bug in playing gallery.
• Gallery and images view has been improved. Now the galleries should show up much faster and working.

Another tiny but problematic query bug

By fixing the previous query bug, the new code caused another 2 tiny bugs which I totally omitted.
The bugs are small but the effects are bad.
In conclusion, it's not really easy to translate the URL into GraphQL queries.