Only an avast user, but my take on this, based only on logic/good practice and what avast has done in the past in related things.

I think that the abort would relate to the deepscreen scan and not the file. I would also expect deepscreen to be activated again if you try to run the file again.

In the past and now, if during a scan avast alerts or in the results of a scan you select do nothing/no action, then avast does nothing. The file remains in place, but avast won’t let you run the suspect file. So my thoughts would be the same for the abort deepscreen.

However, these are only my thoughts and not avast! softwares.

Something that you might consider, enable the Hardened Mode and set it to Aggressive, this checks suspect files against an avast cloud database (if on that database, allowed to run) and it also gives you the option in the notification window to add this file to the exclusions. You have to be 100% sure it is clean before hitting this or you could be risking infection.