[NFR] Make Phalcon\Http\Cookie less depend on session

[ghost]

This can be useful for cases where the application does not need sessions (ie, WordPress does not use sessions):

$di = new \Phalcon\DI();
$di->set('cookies', function () {
        $cookies = new Phalcon\Http\Response\Cookies();
        $cookies->useEncryption(false);
        return $cookies;
});

$di->set('response', function() { return new \Phalcon\Http\Response(); });
$di->getShared('cookies')->set('gift_order', '2221dddd', time()+86400, '/');
$di->getShared('response')->send();

If session is not added to DI, it won't be used — this can be useful in some cases, especially if sessions are stored in the database: if we don't need session, we can save some CPU ticks by not connecting to the database etc.

[phalcon]

If the user set additional options for the cookie, the only way to recover them in a second request is getting those details from the session or some temporal storage where we can place them. Does this disable that feature or make it optional?

[ghost]

Optional: if the session is not provided, it is not used. If it is provided, it will work the same way as before.

The patch tries to make the use of session optional.

There is often no need to send a cookie on every response: one setcookie() is enough for the browser to send cookies on every request until the cookie expires.

[phalcon]

Ok, great!