Add basic programmer's colors

[defr0std]

Coloring the files which programmers are often dealing with:

• Source code files for popular languages. Colored in green like documents because that's what they essentially are.
• Project-like files (c-sharp projects, solutions, etc) stand out in red for an easier identification among the source code files.
• Configuration files (json, yaml, etc) also stand out in yellow for easier identification.
• Common binary files. Colored as temp/ignores because essentially they can be reconstructed from sources.
• Stylesheets colored in magenta to signal that this is UI related. P.S. I'd also propose to color images/videos in magenta too. Then magenta would represent everything "vivid".

The list is not exhaustive, we can add more popular types of files later if needed.

Fixes #22.

[defr0std]

@arcticicestudio, could you please have a look?

[ghost]

Is it possible to create another file for this (ex: src/dir_colors_programming) ? I'm a programmer and I don't like when my 'ls' looks like a christmas tree (personal taste). Can we just keep the "main" src/dir_colors clean and simple please?

[defr0std]

Yeah, I tried to separate this into multiple files, but then the installation process becomes cumbersome. Currently, there is one file that you could symlink and then run dircolors on it, which is very convenient.

With multiple files, we'd need first to merge the files into one. We can add a shell script for it (e.g. install.sh), which would by default merge the files and place the result into ~/.dir_colors. There would be no auto-update on git pull then, but I guess you could always re-run install.sh when needed. After all, this repository does not seem to be updated often.

Invoking dircolors utility twice doesn't work either because it outputs the code "LS_COLORS=xxx", so the second invocation would overwrite the first one, unless we start messing with its output.

P.S. Regarding the christmas tree, I don't like it either and I tried to avoid it as much as possible. For example, most of the source code file combinations are green (like .cc and .h for c++, .ts and .html for frontend, etc), so typically your project would have a single dominant color. The exceptions would be when you have a large mix of source/configuration files (e.g. c++ and text files) in the same folder, but I think this is less common. Directories with images/fonts/stylesheets would also look quite colorful, but that could be ok because you typically need to find something to edit.