feat(fetch): delete --deep option

[MaineK00n]

What did you implement:

The --deep option was to look for CVE information in offensive-security/exploitdb. However, it is an implementation that executes a lot of REST APIs, and it took 22m53s for the whole fetch with --deep option. (Without the --deep option, it was 38s, so the deep option was too slow.

Basically, I believe that the information I want can be obtained from the following two CSVs. These information can be inserted without using the deep option.

• https://raw.githubusercontent.com/offensive-security/exploitdb/master/files_shellcodes.csv
• https://raw.githubusercontent.com/offensive-security/exploitdb/master/files_exploits.csv

Refs #7

Fixed a bug that prevented the opening of links shown in the inserted data.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

How Has This Been Tested?

delete --deep option

// PR
go-exploitdb fetch exploitdb --deep
unknown flag: --deep

fix link

// PR
sqlite> SELECT * FROM documents WHERE exploit_unique_id = 3219;
offensive_security_id|exploit_unique_id|document_url|description|author|type|platform|port
1|3219|https://github.com/offensive-security/exploitdb/blob/master/exploits/osx/local/3219.rb|Apple Mac OSX 10.4.8 (8L2127) - 'crashdump' Local Privilege Escalation|MoAB|local|osx|

$ curl -D - -s -o /dev/null https://github.com/offensive-security/exploitdb/blob/master/exploits/osx/local/3219.rb
HTTP/2 200

// upstream/master
sqlite> SELECT * FROM documents WHERE exploit_unique_id = 3219;
offensive_security_id|exploit_unique_id|document_url|description|author|type|platform|port
2911|3219|https://github.com/offensive-security/exploitdb/exploits/osx/local/3219.rb|Apple Mac OSX 10.4.8 (8L2127) - 'crashdump' Local Privilege Escalation|MoAB|local|osx|

$ curl -D - -s -o /dev/null https://github.com/offensive-security/exploitdb/exploits/osx/local/3219.rb
HTTP/2 404

Checklist:

You don't have to satisfy all of the following.

• Write tests
• Write documentation
• Check that there aren't other open pull requests for the same issue/feature
• Format your source code by make fmt
• Pass the test by make test
• Provide verification config / commands
• Enable "Allow edits from maintainers" for this PR
• Update the messages below

Is this ready for review?: NO

Reference

[kotakanbe]

LGTM