In the patch test, instead of migrating to the current SHA directly.
Migrate to the latest release (with code at the time of release) and
then migrate to last commit in PR.
Why? When directly migrating, the previous patches that would've run
with old code have access to the new code and it's not realistic. This
change brings it a little bit closer to reality. Hence missing failures
that would occur with IRL installations.
* ci: ignore js only changes while running unittests
- IF PR only changes JS files then unittests / patch tests wont run.
- Change done to save resources / concurrent builds.
* ci: ignore md files in build
* Generated v10 backup archive
* used old v7 erpnext backup hosted via build.erpnext.com
* upgraded to v10 frappe + erpnext
* uninstalled and deleted erpnext related data
* Hosted backup on https://frappeframework.com/files/v10-frappe.sql.gz
