docs(documentation): Replace all occurrence of specVersion 4.0 with 5.0

Author: RandomByte

packages/documentation/docs/pages/OpenUI5.md

@@ -27,7 +27,7 @@ ui5 add sap.ui.core sap.m sap.ui.table themelib_sap_fiori_3
 
 **Example ui5.yaml of an application**
 ```yaml
-specVersion: "4.0"
+specVersion: "5.0"
 type: application
 metadata:
   name: some.project.name
@@ -43,7 +43,7 @@ framework:
 
 **Example ui5.yaml of a library**
 ```yaml
-specVersion: "4.0"
+specVersion: "5.0"
 type: library
 metadata:
   name: some.library

packages/documentation/docs/pages/SAPUI5.md

@@ -40,7 +40,7 @@ ui5 add -D sap.ushell
 
 **Example ui5.yaml of an application**
 ```yaml
-specVersion: "4.0"
+specVersion: "5.0"
 type: application
 metadata:
   name: some.project.name
@@ -58,7 +58,7 @@ framework:
 
 **Example ui5.yaml of a library**
 ```yaml
-specVersion: "4.0"
+specVersion: "5.0"
 type: library
 metadata:
   name: some.library

packages/documentation/docs/pages/extensibility/CustomServerMiddleware.md

@@ -15,7 +15,7 @@ A middleware may be executed before or after any other middleware. This can eith
 ### Example: Basic configuration
 
 ```yaml
-specVersion: "4.0"
+specVersion: "5.0"
 type: application
 metadata:
   name: my.application
@@ -45,7 +45,7 @@ A custom middleware extension consists of a `ui5.yaml` and a [custom middleware
 ### Example: ui5.yaml
 
 ```yaml
-specVersion: "4.0"
+specVersion: "5.0"
 kind: extension
 type: server-middleware
 metadata:
@@ -65,7 +65,7 @@ The UI5 Server will detect the custom middleware configuration of the project an
 
 ```yaml
 # Project configuration for the above example
-specVersion: "4.0"
+specVersion: "5.0"
 kind: project
 type: application
 metadata:
@@ -76,7 +76,7 @@ server:
       beforeMiddleware: serveResources
 ---
 # Custom middleware extension as part of your project
-specVersion: "4.0"
+specVersion: "5.0"
 kind: extension
 type: server-middleware
 metadata:

packages/documentation/docs/pages/extensibility/CustomTasks.md

@@ -20,7 +20,7 @@ Another custom task called `render-markdown-files` is then executed immediately
 
 ```yaml
 # In this example configuration, two custom tasks are defined: 'babel' and 'render-markdown-files'.
-specVersion: "4.0"
+specVersion: "5.0"
 type: library
 metadata:
   name: my.library
@@ -41,7 +41,7 @@ You can also connect multiple custom tasks with each other. The order in the con
 
 ```yaml
 # In this example, 'my-custom-task-2' gets executed after 'my-custom-task-1'.
-specVersion: "4.0"
+specVersion: "5.0"
 type: library
 metadata:
   name: my.library
@@ -60,7 +60,7 @@ A custom task extension consists of a `ui5.yaml` and a [task implementation](#ta
 ### Example: ui5.yaml
 
 ```yaml
-specVersion: "4.0"
+specVersion: "5.0"
 kind: extension
 type: task
 metadata:
@@ -80,7 +80,7 @@ The task extension will then be automatically collected and processed during the
 
 ```yaml
 # Project configuration for the above example
-specVersion: "4.0"
+specVersion: "5.0"
 kind: project
 type: library
 metadata:
@@ -94,7 +94,7 @@ builder:
             firstH1IsTitle: true
 ---
 # Task extension as part of your project
-specVersion: "4.0"
+specVersion: "5.0"
 kind: extension
 type: task
 metadata:

packages/documentation/docs/pages/extensibility/ProjectShims.md

@@ -5,20 +5,20 @@ Also see [RFC 0002 Project Shims](https://github.com/UI5/cli/blob/main/rfcs/0002
 
 #### Structure
 ```yaml
-specVersion: "4.0"
+specVersion: "5.0"
 kind: extension
 type: project-shim
 metadata:
   name: <name of project shim extension>
 shims:
   configurations:
     <module name (id)>:
-      specVersion: "4.0"
+      specVersion: "5.0"
       type: <project type>
       metadata:
         name: <project name>
     <module name (id)>:
-      specVersion: "4.0"
+      specVersion: "5.0"
       type: <project type>
       metadata:
         name: <project name>
@@ -61,20 +61,20 @@ An application "my-application" defines a npm dependency to [lodash](https://lod
 
 **ui5.yaml**
 ```yaml
-specVersion: "4.0"
+specVersion: "5.0"
 type: application
 metadata:
   name: my.application
 --- # Everything below this line could also be put into the ui5.yaml of a standalone extension module
-specVersion: "4.0"
+specVersion: "5.0"
 kind: extension
 type: project-shim
 metadata:
   name: my.application.thirdparty
 shims:
   configurations:
     lodash: # name as defined in package.json
-      specVersion: "4.0"
+      specVersion: "5.0"
       type: module # Use module type
       metadata:
         name: lodash
@@ -142,30 +142,30 @@ application-a/
 The shim defined in the application configures the legacy libraries and defines their dependencies. This shim might as well be a standalone module that is added to the applications dependencies. That would be the typical reuse scenario for shims.
 
 ```yaml
-specVersion: "4.0"
+specVersion: "5.0"
 type: application
 metadata:
   name: application.a
 ----
-specVersion: "4.0"
+specVersion: "5.0"
 kind: extension
 type: project-shim
 metadata:
   name: legacy-lib-shims
 shims:
   configurations:
     legacy-library-a:
-      specVersion: "4.0"
+      specVersion: "5.0"
       type: library
       metadata:
         name: legacy.library.a
     legacy-library-b:
-      specVersion: "4.0"
+      specVersion: "5.0"
       type: library
       metadata:
         name: legacy.library.b
     legacy-library-x:
-      specVersion: "4.0"
+      specVersion: "5.0"
       type: library
       metadata:
         name: legacy.library.x