feat: name embedded json according the general convention

[stiebitzhofer]

Description

What keywords did you search in schema-tools issues before filing this one ?

Is this a BUG REPORT or FEATURE REQUEST ?
FEATURE

Environment:
https://app.s1seven.co

What you expected to happen:
Currently, the name of the JSON embedded is certificate.json. It should be named according to the general convention <SellerName>-<Certificate Number>.pdf.

The functions of @s1seven/certificate-summary shall be used.

[christophbuehler]

@stiebitzhofer Certificate Number = certificateIdentifier?

Which option to you like best?

Seller name: Green Plastics AG
Certificate Identifier: 43

---

a) Green Plastics AG-43.pdf ← as specified
b) green-plastics-ag-43.pdf ← replace spaces with - and lowercase
c) green_plastics_ag-43.pdf ← replace spaces with _ and lowercase

---

To be honest, I like something generic like "certificate.pdf" better than any of those:

• Makes the file much easier to extract programmatically
• The file name is more descriptive than a company name and an integer
• No issues with unexpected values (not everything is a valid file name in every environment, so we need to sanitize it)

Maybe some combination with a prefix like certificate-?

[stiebitzhofer]

In the emails, we name it "GreenPlasticsAG-CN-43.json". CN for Certificate Number. I never like it if file names for downloads are always the same. Okay?