Add curl advisories importer

[ambuj-1211]

This pr resolves the issue #1166.
The advisories were added properly and the site was working fine. I also registered the importer in the init.py file.

[ambuj-1211]

@TG1999 please let me know if there are any further changes and everything is correct or not.

[ziadhany]

@ambuj-1211 This is a good start but try to make use of all available data ex: details, CWE , ..

[ambuj-1211]

on it

[ambuj-1211]

@ziadhany @TG1999 Done with the changes as mentioned.

[ziadhany]

@ambuj-1211 Nice work! just a few nits for your consideration.

[ziadhany]

@ambuj-1211 please add a curl improver to the valid_versions.py

ex: https://github.com/nexB/vulnerablecode/blob/main/vulnerabilities/improvers/valid_versions.py#L472

[ambuj-1211]

work! just a few nits for your consi

I think you tagged someone else in this comment, is it a mistake?
And I am working on the changes now.

[ziadhany]

work! just a few nits for your consi

I think you tagged someone else in this comment, is it a mistake?
And I am working on the changes now.

sorry it was a mistake and I fixed it

[ambuj-1211]

@ziadhany please review the changes and do let me know.

[ziadhany]

Great work! please fix those failing tests then squash the commits

[ambuj-1211]

@ziadhany I made the changes, should I also update my branch?

[ziadhany]

@ambuj-1211 Absolutely! Once all the changes are in place, squashing them into a single commit before merging will create a cleaner history for everyone.

to fix the test update the vulnerabilities/tests/test_data/curl/expected-curl-advisory-output.json
and it would be good if you add more test examples :
vulnerabilities/tests/test_data/curl/expected-curl-advisory-output1.json
vulnerabilities/tests/test_data/curl/expected-curl-advisory-output2.json

[ambuj-1211]

@ziadhany @TG1999 i have made all the required changes and squashed all the commits to make the history clean, moreover I also had updated my branch according to the main branch.
Please review it.

[ambuj-1211]

@ziadhany some checks are not successfull but they are because of openssl url do I need to change it to some thing, I am asking because it is not related to curl advisories.

[ziadhany]

@ziadhany some checks are not successfull but they are because of openssl url do I need to change it to some thing, I am asking because it is not related to curl advisories.

@ambuj-1211 No, this is the docs test ( not related to this pull request )

[ambuj-1211]

so this pr is good to go?

[ziadhany]

LGTM, just a minor nit for your consideration

[ambuj-1211]

@ziadhany check the files now I have changed the files and squashed the commits, I think now the history and everything is clean and good to go, please let me know if there are any more nits.