graceful restart should be skipped on fuse option change.

[zhoucheng361]

What happened:

root@bench-01:~/juicefs# git checkout test-version-upgrade
root@bench-01:~/juicefs# .github/scripts/command/version_upgrade.sh test_update_fuse_option
root@bench-01:~/juicefs# ps -ef | grep mount
root     1985713       1  0 11:28 ?        00:00:00 ./juicefs mount -d sqlite3:///root/juicefs/test.db /tmp/jfs_xattr --enable-xattr
root     1985725 1985713  1 11:28 ?        00:00:00 /root/juicefs/juicefs mount -d sqlite3:///root/juicefs/test.db /tmp/jfs_xattr --enable-xattr
root     1985766       1  0 11:28 ?        00:00:00 ./juicefs mount -d sqlite3:///root/juicefs/test.db /tmp/jfs_xattr
root     1985778 1985766  1 11:28 ?        00:00:00 /root/juicefs/juicefs mount -d sqlite3:///root/juicefs/test.db /tmp/jfs_xattr
root     1985819       1  1 11:28 ?        00:00:00 ./juicefs mount -d sqlite3:///root/juicefs/test.db /tmp/jfs_xattr --enable-xattr
root     1985831 1985819  2 11:28 ?        00:00:00 /root/juicefs/juicefs mount -d sqlite3:///root/juicefs/test.db /tmp/jfs_xattr --enable-xattr
root     1985851 1896090  0 11:29 pts/2    00:00:00 grep --color=auto mount

What you expected to happen:
should have only two mount process after script run.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?

Environment:

• JuiceFS version (use juicefs --version) or Hadoop Java SDK version:
• Cloud provider or hardware configuration running JuiceFS:
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Object storage (cloud provider and region, or self maintained):
• Metadata engine info (version, cloud provider managed or self maintained):
• Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
• Others: