Update instance name in backup file when importing new instance

[MusicDin]

When new instance is imported, instance and volume names are updated in backup.yaml file to match the new instance name.

Fixes #12065

[MusicDin]

@tomponline

Test

Should I add a test for recovering imported instances (that will ensure the above issue does not happen again)? If so, should I put in test/suites/backup.sh?

Projects

While project in backup.yaml is not respected on import (only --project flag is), I think we should still update the project occurrences in backup file on import?

---

Another (unrelated) issue is when an instance is created in a project, but no instance name is provided.

$ lxc launch ubuntu:22.04
Creating the instance
Instance name is: lenient-llama
Starting lenient-llama

$ lxc launch ubuntu:22.04 --project test
Creating the instance
Instance name is: steady-seasnail?project=test
Starting steady-seasnail?project=test
Error: Instance not found

$ lxc launch ubuntu:22.04 c123 --project test
Creating c123
Starting c123

If this is not the expected behavior, I can fix it in another PR?

[tomponline]

Should I add a test for recovering imported instances (that will ensure the above issue does not happen again)? If so, should I put in test/suites/backup.sh?

Yes please

[tomponline]

$ lxc launch ubuntu:22.04 --project test

Good spot! Lets fix that :)

[tomponline]

While project in backup.yaml is not respected on import (only --project flag is), I think we should still update the project occurrences in backup file on import?

Agreed, good idea. It should represent the project its imported into.