Version 8.6.7

Magic (main)

Significantly stablised Magic on Windows machines, by creating a QA document, I have
been following to the last detail, exposing several severe errors, particularly with
Visual Studio, SQL Server, and Windows based development. If you previously had issues
with testing Magic with SQL Server, Visual Studio, or on Windows - This release
probably fixes your problems.

Removed the ability to configure which database to use for authentication and logging,
since I suspect it's never used with anything but the default version anyways, and it
only complicated the code and made it more difficult to understand.

Created the ability to configure a public crypto key as "enabled" or not, implying
if it's not enabled, no invocations cryptographically signed with that key will be
accepted by the server.

Fixed some minor errors in administrating your users that wouldn't propagate errors
to the user, making errors invisible for the end user as he tries to administrate
his users.

Fixed a lot of cryptography errors related to SQL Server. Basically, the cryptographic
signed invocations didn't work at all on SQL Server due to an erronously added "dbo"
prefix in their endpoint URLs.

Made it simpler to start Magic backend on Windows with Visual Studio by removing IIS
profile entirely, and only relying upon kestrel/backend profile.

Fixed initial debugging of backend on Visual Studio such that it now shows (opens) the
ping endpoint by default as you start the backend.

Breaking change - Added some changes to the magic database script, specifically
added the ability to have a boolean flag (enabled) for the crypto_keys database table.
Either apply the changes for this specific column, or drop and re-create your magic database
as you install this version. Also created new "magic_version" database table, to keep
track of versioning in the future, and hopefully be able to create some sort of database
migration script(s) logic in future releases - To avoid having to drop and re-create
database every time users installs a new version. Hence, hopefully this will be the last
time you'll have to drop your Magic database, and/or manually migrate it.

magic.lambda.logging

Removed the ability to configure which database to persist log entries into, since
it only complicates the code, and I suspect it's never really actually used with anything
but the default value.

magic.lambda.strings

Removing arguments after invocation to [strings.concat].

magic.lambda

Removing arguments after invocation to [add], [insert-before] and [insert-after].

Added [context] slot, allowing Hyperlambda code to dynamically add values onto the stack.
Also added [get-context] that retrieves dynamically added objects from the stack.
Notice, a dynamically created stack object will not interfer with C# created stack objects,
and Hyperlambda cannot retrieves C# created stack objects either. This is to make it impossible
for Hyperlambda code to "clash" with C# created stack objects, and/or manipulate such.

Added support for "fromBase64" type in [convert], which will assume the given value
is a base64 encoded byte[], and convert it back to such, and return to the caller.