deps: follow openkal 0.7.0 (#3)

* deps: follow openkal 0.7.0

规范新增 `openkal.random`(mcpplibs/openkal#8),版本升到 0.7.0。

⚠️ CI 有一道版本同步门,而它的诊断说明了为什么必须一起改:

    this is openkal 0.7.0 and this implementation is written against
    openkal 0.6.0. Nothing is wrong with either; they are not in step.

⭐ 本包**不提供** `openkal.random`,而那不是偏离 —— 6.1 条规定实现提供一个
接口是全有或全无,不提供的接口作为链接期定义缺席。这里跟随的只是规范版本,
不是接口集合。

* release: 0.1.3

The branch carried 0.1.2, which is the version on `main` and the version
already in the index. Following openkal 0.7.0 changes what this package
declares, and on two of these repositories it also adds an interface, so
the content behind that number is no longer the content published under
it.

openkal takes a minor bump for a new interface and an implementation
following it takes a patch bump --- the shape of 0.5.2 → 0.6.0 with
0.5.2 → 0.5.3 beneath it.

* fix(ci): one specification in the graph

The example asked for openkal 0.6.0 while the package it links asks for
0.7.0. Both were resolved, the engine fell back to mangling one copy's
module names so they could coexist, and mangling stages sources without
the headers beside them:

    src/kal.cpp:32:10: fatal error: uefi.h: No such file or directory

Naming one specification removes the fallback.

Author: Sunrisepeak

examples/hello/mcpp.toml

@@ -11,5 +11,5 @@ target  = "x86_64-windows-gnu"
 ldflags = ["-nostdlib", "-Wl,--subsystem,10", "-Wl,-e,efi_main"]
 
 [dependencies]
-openkal = "0.6.0"
+openkal = "0.7.0"
 openkal-uefi = { path = "../.." }

mcpp.toml

@@ -15,7 +15,7 @@
 [package]
 namespace   = "mcpplibs"
 name        = "openkal-uefi"
-version     = "0.1.2"
+version     = "0.1.3"
 description = "An implementation of openkal on UEFI Boot Services, for applications the firmware loads before an operating system exists"
 license     = "Apache-2.0"
 
@@ -32,7 +32,7 @@ authors     = ["mcpplibs"]
 repo        = "https://github.com/mcpplibs/openkal-uefi"
 
 [dependencies]
-openkal = "0.6.0"
+openkal = "0.7.0"
 
 [build]
 flags = [