Add support for creating strong_ptr's to `static` memory/objects

[kammce]

Users should be able to create type safe pointers from objects with static storage duration without the cost of a control block within RAM. The state of a strong_ptr that points to a static object should be that its m_ctrl field is set to nullptr. Having a control block set to nullptr would represent infinite lifetime for the object/memory.

There is potential to use this to protect the memory resources that each strong_ptr's ref_info holds, allowing the lifetime of the allocator itself to be extended until the last object it allocated is destroyed.

[kammce]

I should also specify what happens to weak and optional ptr

optional_ptr

An optional pointer with a nullptr for m_ctrl is also considered pointing to a static object/memory. Everything else should just work as expected.

weak_ptr

Weak_ptr also has the same layout as the rest of the smart pointers, so it can follow suit with optional_ptr. A weak_ptr to a static object, will always be lockable and will never be expired. Meaning the expire function would need to change to support a null m_ctrl with a non-null m_value.