[RFC] Stage 2: Introducing new fields in file/dll/process fields

[AsuNa-jp]

• Have you signed the contributor license agreement?
  Yes
• Have you followed the contributor guidelines?
  Yes
• For proposing substantial changes or additions to the schema, have you reviewed the RFC process?
  Yes
• If submitting code/script changes, have you verified all tests pass locally using make test?
• If submitting schema/fields updates, have you generated new artifacts by running make and committed those changes?
  Yes
• Is your pull request against main? Unless there is a good reason otherwise, we prefer pull requests against main and will backport as needed.
  Yes
• Have you added an entry to the CHANGELOG.next.md?
  Yes

[github-actions]

It looks like this PR modifies one or more .asciidoc files. These files are being migrated to Markdown, and any changes merged now will be lost. See the migration guide for details.

[mjwolf]

@AsuNa-jp Can you add a changelog entry in CHANGELOG.next.md?

[AsuNa-jp]

Hi @mjwolf
Thank you very much for the feedback. I've added changelog entry to CHANGELOG.next.md and added beta: This field is beta and subject to change. to all of the newly added fields.

I also added an example of how file origin information is added when downloading a file from a web browser on macOS. Let me know if you need additional examples.

For process.executable see my reply at #2441 (comment)

[github-actions]

Warning

It looks like this PR modifies one or more .asciidoc files. These files are being migrated to Markdown, and any changes merged now will be lost. See the migration guide for details.