Add ydb_terminate() as a user-callable function to force YDB engine cleanup
Final Release Note
Description
Currently we have ydb_exit() but it can "error out" for non-catastrophic issues (e.g. a transaction is pending) thus bypassing the cleanup that is needed in situations where ydb_exit() is being driven as part of a final cleanup handler of some sort. This is the situation with Golang where we currently advocate 'defer yottadb.Exit()' which drive ydb_exit() as the Golang process is about to shutdown. This situation cannot tolerate errors so we will create another routine (ydb_terminate()) which operates like ydb_exit() but is fault tolerant and will do all the rundown it can without stopping on less than a fatal error.