repo: move packages under their SBo category

Mirror SBo's own <category>/<package>/ layout instead of a flat
<package>/ one. The category is now carried by the directory, so
there's no separate map to maintain, and a package exports to the SBo
repo at the identical relative path.

misc:    SecLists, exploitdb, nuclei
games:   UrbanTerror
network: feroxbuster, ffuf, gobuster, metasploit-framework-bin, r8125

Categories taken from the synced SBo tree, which is authoritative.

This also repairs two things the flat layout had broken:

- test-build's category_of() returned "." for every package, since it
  derives the category from the parent directory name.
- post-commit asserted a fixed depth. It now locates a build by the
  directory holding the .SlackBuild, and names the archive after the
  package with the package dir at the tarball root, as SBo expects.

Drops the exec bit from SecLists.SlackBuild and gobuster.SlackBuild,
flagged by sbolint once the pre-commit hook started running: SBo
requires 0644 and ships both that way.

1 files changed, 19 insertions, 0 deletions

diff --git a/misc/SecLists/slack-desc b/misc/SecLists/slack-desc
new file mode 100644
index 0000000..358ec62
--- /dev/null
+++ b/misc/SecLists/slack-desc
@@ -0,0 +1,19 @@
+# HOW TO EDIT THIS FILE:
+# The "handy ruler" below makes it easier to edit a package description.
+# Line up the first '|' above the ':' following the base package name, and
+# the '|' on the right side marks the last column you can put a character in.
+# You must make exactly 11 lines for the formatting to be correct.  It's also
+# customary to leave one space after the ':' except on otherwise blank lines.
+
+        |-----handy-ruler------------------------------------------------------|
+SecLists: SecLists (the security tester's companion.)
+SecLists:
+SecLists: It's a collection of multiple types of lists used during security
+SecLists: assessments, collected in one place.
+SecLists: List types include usernames, passwords, URLs, sensitive data
+SecLists: patterns, fuzzing payloads, web shells, and many more.
+SecLists: The goal is to enable a security tester to pull this repository
+SecLists: onto a new testing box and have access to every type of list
+SecLists: that may be needed.
+SecLists:
+SecLists: Repository: https://github.com/danielmiessler/SecLists