Support period in lora name

[arledesma]

Fixes #75

[colinurbs]

Thank you this looks solid. Just going to try it real quick and then merge it into main.

[colinurbs]

Actually ended up having an error during the actual lora loading. I wonder if peft can't handle the "." and we need to at least rename it internally.

Loading pixar_7.epochs was unsucessful with the following error:
'module name can\'t contain ".", got: pixar_7.epochs'
Traceback (most recent call last):
  File "/home/colin/FramePack/studio.py", line 571, in worker

[arledesma]

@colinurbs I'll test some more. I had a dirty branch with a ton of local changes and I ended up partial staging this patch.

[arledesma]

@colinurbs Seems to work with this last change.

I'm not sure if this is a great way to handle it with the type of audience that is currently using the codebase. The suggested method is to just remove every ., as seen in pytorch/vision#474. I don't know if that would be a good idea though as people have multiple versions of these lora's that may simply have a minor version change. Long term it may be a good idea to replace this hack with some simple metadata that permits the user to safely name the module.

[arledesma]

Will need further testing. I'll set up a clean install and run through a few scenarios in the next day or so, unless you have time to go through the tests.

1. Single lora, no period, must continue to work.

2. Multiple lora, no period, must continue to work.

3. Cancellation for 1 and 2 must continue to work.

4. Single lora, period in name, should work

5. Multiple lora, period in name, should work.

6. Multiple lora, mixture of period and no period, should work.

7. Cancellation for 4, 5, 6 should work.

8. Any additional jobs queued must continue to work.

9. Any point that lora's are unloaded must continue to unload the lora, regardless of period in the name

[arledesma]

@colinurbs manual tests passed.

The only time that the tests failed was when a cancellation was sent while sample_hunyuan was performing work prior to invoking the callback, leading to the KeyboardInterrupt in the callback that just leaves the application in an unusable state - gradio still functions but the queue system was basically dead. Let me know if you need a separate issue to track that.

[colinurbs]

Yeah please open a ticket for that. Thanks for your testing!