chore!: homogenize shell scripting sections across files

[davorpa]

What does this PR do?

Improve repo

For resources

Description

moving all "shell scripting" languages and utils into same section. E.g.

• Bash
• Shell
• PowerShell
• Batch
• Awk
• Sed

Sorry for this little outscope: removing some and in creators list as remainings of #7034 (part of it conflicts merge commit b328827)

Checklist:

• Read our contributing guidelines.
• Include author(s) and platform where appropriate.
• Put lists in alphabetical order, correct spacing.
• Used an informative name for this pull request.

Follow-up

• Check the status of GitHub Actions and resolve any reported warnings!

[eshellman]

I don't think having one big section for "shell scripting" is wise. awk and sed are languages on their own. mixing bat and sh in the same section will be disliked only by Windows and *nix users. And what about applescript?

[davorpa]

I don't think having one big section for "shell scripting" is wise. awk and sed are languages on their own. mixing bat and sh in the same section will be disliked only by Windows and *nix users. And what about applescript?

@eshellman Is this close definitely? Can I reopen this and reorganize it in subsections? I mean...

• Shell scripting
  • AppleScript
  • BeanShell
  • Awk
  • Bash
  • PowerShell
  • Sed

What do you think? Better?

[eshellman]

probably a good idea to create an issue for discussion before putting work into a reorganization.

categories should be arranged in a way that helps people find what they're looking for. someone looking for an awk book won't think of looking in a "shell scripting" section, and it won't help them to have Applescript and powershell in the same section.

Try to think of the sections not a a map of concepts but as a map of users.