discuss enhancements for the CAPE extractor

Nobody has claimed this yet.

This issue will serve to keep track of enhancements that are to-be-added to the CAPE extractor after basic functionality is achieved.

For the time being, the current features are in queue:
- [x] **make the report-parsing more modular**: for the time being, the cape extractor parses the report in a simplistic manner; an empty dictionary is instantiated, and then artifacts are added to it one by one, which will make updating it a hard task. Therefore, it would be nice to have a global list of artifacts containing the artifact's name and location within the report, as well as a method that goes through that list and extract the necessary artifacts; this will make it easier to support other extractors that provide similar reports.
- [ ] **add the ability to support sample submission**: add a class method that takes in a filename, an api url, and an api key, and returns a CAPE extractor object.
- [x] **make it easier to generate cape extractor objects from a filename**: consider adding a helper function that takes in a filename and returns a CAPE extractor object.

Locate the CAPE extractor implementation and the existing helper that creates extractor objects from filenames. Review how extractor inputs and API requests are handled, then add the requested filename, API URL, and API key entry point; done means it returns a CAPE extractor object for a submitted sample.

Written by the indexing model from the issue text.