asfa: init at 0.10.0

[obreitwi]

Description of changes

• add new package: asfa at latest version

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/), also working my personal setup
• 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[AndersonTorres]

We do not use Semantic Versioning.

Reword the commit according to the Contributing Guidelines - the one you checked.

[TomaSajt]

Hey! Thanks for taking your time to contribute.

Could you update the PR title/commit message to use the commit message conventions listed inside pkgs/README.md?
It would be something like: <package>: init at <version>

Edit: looks like I was too slow in sending the message :)

[TomaSajt]

I've left some additional change suggestions.

Also, consider formatting the file using nixfmt-rfc-style.
It's the soon-to-be default across nixpkgs.
Doing this helps avoid unnecessarily big diffs when the tree-wide formatting happens sometime in the future.

[TomaSajt]

LGTM

[AndersonTorres]

Besides, LGTM