create_infotext allow index and callable, re-work Hires prompt infotext

[w-e-w]

Description

• as mentioned briefly in fix issue with Styles when Hires prompt is used #15269 I plan to rework create_infotext

this PR allows for generation parameters be a list string or callable, this enables much more flexibility and extensibility on how future infotax can be written

• for detail, reference the docstring e3aabe6

• this PR also includes reworking of the Hires prompt infotext from fix issue with Styles when Hires prompt is used #15269, it is now implemented as a callable outside this funcrion

with this PR will be easier to add new parameters without directly adding extra bulk to this function

---

further work in future PR after this is merged
with this PR is possible to clean up some of the non-shared parameters from within the function
fore example Token merging ratio hr only applicablefor txt2img when hires fix is enabled, it seems appropriate to move the definition out of this shared function

other changes

• when use_main_prompt is true index is set to 0`
  I believe this makes sense
• Processed.js > json.dumps will output None when encountering non-zerizable objects such as functions
• add docstring for create_infotext

---

note
I initially was planning for this to be done before before 1.9-RC, as this includes the removal of the two new arguments all_hr_prompts and all_hr_negative_prompts that I added in #15269, reason being if there are pushed to master then back was completely would ideally need to be kept
if possible I would like this to be pushed to 1.9-RC

Checklist:

• I have read contributing wiki page
• I have performed a self-review of my own code
• My code follows the style guidelines
• My code passes tests

[bluelovers]

this pr make other extensions can't save list in pnginfo

[w-e-w]

this pr make other extensions can't save list in pnginfo

no this does not
a python list was never supported by the infotext syntax

a demo of why this is the case

when your infotext contains a list

import json

def quote(text):
    if ',' not in str(text) and '\n' not in str(text) and ':' not in str(text):
        return text
    return json.dumps(text, ensure_ascii=False)
infotext_dict = {
    'test': 'my test',
    'test list': ['a', 'b', 'c'],
}

infotext = ", ".join([k if k == v else f'{k}: {quote(v)}' for k, v in infotext_dict.items() if v is not None])

even though the generating infotext DOSE contain a list like so

test: my test, test list: ["a", "b", "c"]

this is NOT a valid valid infotext

when the infotext if paresd by modules.infotext_utils.py.parse_generation_parameters()

the anything after the first , comma in the list will be lost during parseing

---

if you wish to make it dictionary or list work in infotext it, it needs to be first encoded into some data structure like json before it's past the info text
I have a PR proposal on system for this and a way to add structal data to infotext but it was not approved

• Compact infotext system, Compact soft inpainting infotext #14731

there's also a way for extension to add structured data without the built-in from the PR system
I have written a demo
https://github.com/w-e-w/sd-webui-infotext-example/blob/main/scripts/infotext_example_advance.py

essentially a list or dict will have to be encode in some kinde some sort of structure string for example json

infotext_dict = {
    'test': 'my test',
    'test list': json.dumps(['a', 'b', 'c']),
}

output

test: my test, test list: "[\"a\", \"b\", \"c\"]"

since the excessive use of \ in my implementation it also employees quote_swap = str.maketrans('\'"', '"\'')

quote_swap = str.maketrans('\'"', '"\'')

infotext_dict = {
    'test': 'my test',
    'test list': json.dumps(['a', 'b', 'c']).translate(quote_swap),
}

the result in final output is

test: my test, test list: "['a', 'b', 'c']"

later on during parseing of info text, extra logic is added to parse out the json

---

you can use any other structure if you like as long as it is a string
for example CSV

---

summary
list or dict is not supporting nativity by infotext
ONLY string are allowed to be stored in the values
if you wish to encode other data types then it needs to be encoded as a string using some data format
later on string should be decoded using script_callbacks.on_infotext_pasted