interpreter: move handling of module stability to interpreter

Thanks to `ModuleInfo`, all modules are just named `foo.py` instead of
`unstable_foo.py`, which simplifies the import method a bit. This also
allows for accurate FeatureNew/FeatureDeprecated use, as we know when
the module was added and if/when it was stabilized.

2 files changed, 2 insertions, 2 deletions

diff --git a/test cases/keyval/1 basic/meson.build b/test cases/keyval/1 basic/meson.build
index 4207b8e..a6e023e 100644
--- a/test cases/keyval/1 basic/meson.build
+++ b/test cases/keyval/1 basic/meson.build
@@ -1,4 +1,4 @@
-project('keyval basic test')
+project('keyval basic test', meson_version : '>= 0.55')
 
 k = import('keyval')
 conf = k.load('.config')
diff --git a/test cases/keyval/1 basic/test.json b/test cases/keyval/1 basic/test.json
index dbdc5af..1f8fd9b 100644
--- a/test cases/keyval/1 basic/test.json
+++ b/test cases/keyval/1 basic/test.json
@@ -1,7 +1,7 @@
 {
   "stdout": [
     {
-      "line": "WARNING: Module unstable-keyval is now stable, please use the keyval module instead."
+      "line": "test cases/keyval/1 basic/meson.build:3: WARNING: Project targets '>= 0.55' but uses feature introduced in '0.56.0': module keyval as stable module. Consider either adding \"unstable-\" to the module name, or updating the meson required version to \">= 0.56.0\""
     }
   ]
 }