add mime support (form api is deprecated according to libcurl)

[tsnoam]

libcurl considers the form api deprecated.
in curl_formadd(3) one of the first lines says:

This function is deprecated. Use curl_mime_init(3) instead.

This pull requests implements a safe wrapper of the mime api, keeping simplicity in mind. Usage is quite straight forward.

The following example is a bit simplified (lot of unwraps, usage of &str where possible.

fn main() {
    let filenames = &[ "/path/to/file1", "/path/to/file2" ];
    curl::init();
    let mut client = curl::easy::Easy::new();

    // interesting part starts here

    let mut mime = client.add_mime();
    for fname in filenames.iter() {
        let buf = read_file(fname)?;  // 
        mime.add_part()
            .set_name("some-name").unwrap()
            .set_filename(fname.rsplit_once('/').unwrap().1).unwrap()
            .set_data(buf).unwrap()
            .set_content_type("application/octet-stream").unwrap();
    }
    mime.post()?;

    // make sure not to call client.post/get/put/custom_request() as it will modify stuff inside libcurl causing it to behave
    // not as you intended (this comment is also true fort the deprecated form api)

    // interesting part ends here

    client.url("http://127.0.0.1/").unwrap();
    client.perform().unwrap();
}

/// Read a file into Vec<u8> - implementation is an exercise for the reader
fn read_file(fname: &str) -> Result<Vec<u8>, Error> {
    todo!();
}

[sagebind]

We support linking against libcurl versions older than 7.56.0 (when the mime API was added) so this will need to be behind an opt-in feature to avoid breaking compatibility with those older versions.

[sagebind]

mime is kinda its own API that isn't specific to the easy API, so I would make mime a top-level module.

[tsnoam]

I can see what you're saying about "kinda its own API".
However, mime API doesn't have a meaning without the easy API, quite similar to the form API. So basically, I've put the mime module in the same level as the form module.

I don't mind extracting it, just thought it is worth double checking this before doing so.

Your call though, I'll do what you ask :)

[sagebind]

Only one mime object should be attached to an easy handle at a time since CURLOPT_MIMEPOST replaces any previously assigned mime, so this doesn't seem like it needs to be a Vec.

This should also probably go inside Inner like everything else.

I would also prefer to avoid a raw pointer here since that requires multiple implementations handling the calling of curl_mime_free in multiple places. I wonder if there is a way of keeping the drop code in the Mime struct?

[tsnoam]

Ok. Done.

[tsnoam]

We support linking against libcurl versions older than 7.56.0 (when the mime API was added) so this will need to be behind an opt-in feature to avoid breaking compatibility with those older versions.

Ok. Done.

[tsnoam]

@sagebind
I've adhered to your comments (except for the one I replied with a question of my own).
Is there anything else you would to see?

[bdbai]

Hi @sagebind is there anything else blocking this PR?