hardfault_log:Not having a ulog file to append to is not an error
hardfault_log:Not having a ulog file to append to is not an error

   The hardfault keeps track of the number of reboot without a
   commit to disk. A commit to disk is the act of writing the
   fault data from the bbsram to the hardfault file, not the
   ulog file. The sucessful commit rearms the hardfault system.

   When ulog appending was added it treated the lack of a ulog
   file as an error. This prevented the hardfault_log reset
   from being called because the hardfault_log commit returned
   an error.

   	if hardfault_log check
	then
		if hardfault_log commit
		then
			hardfault_log reset
		fi
	fi

   This change treats the lack a a ulog as a non error.

Aerotenna/Firmware,jlecoeur/Firmware,jlecoeur/Firmware,jlecoeur/Firmware,acfloria/Firmware,mje-nz/PX4-Firmware,jlecoeur/Firmware,acfloria/Firmware,Aerotenna/Firmware,krbeverx/Firmware,dagar/Firmware,jlecoeur/Firmware,mje-nz/PX4-Firmware,mcgill-robotics/Firmware,Aerotenna/Firmware,Aerotenna/Firmware,mcgill-robotics/Firmware,dagar/Firmware,acfloria/Firmware,mje-nz/PX4-Firmware,krbeverx/Firmware,dagar/Firmware,PX4/Firmware,mje-nz/PX4-Firmware,mje-nz/PX4-Firmware,dagar/Firmware,PX4/Firmware,mcgill-robotics/Firmware,krbeverx/Firmware,krbeverx/Firmware,Aerotenna/Firmware,krbeverx/Firmware,acfloria/Firmware,acfloria/Firmware,mcgill-robotics/Firmware,PX4/Firmware,krbeverx/Firmware,PX4/Firmware,jlecoeur/Firmware,dagar/Firmware,PX4/Firmware,PX4/Firmware,jlecoeur/Firmware,mcgill-robotics/Firmware,krbeverx/Firmware,mje-nz/PX4-Firmware,PX4/Firmware,acfloria/Firmware,Aerotenna/Firmware,acfloria/Firmware,Aerotenna/Firmware,mcgill-robotics/Firmware,mje-nz/PX4-Firmware,mcgill-robotics/Firmware,jlecoeur/Firmware,dagar/Firmware,dagar/Firmware