Update docs to be clear about OpenAPI Hub only for swagger (#26669)

* no openAPI Hub for TS

* caps

Author: maririos

.github/PULL_REQUEST_TEMPLATE/control_plane_template.md

@@ -20,7 +20,7 @@ If you need further help with anything, see `Getting help` section below.
 
 What's the purpose of this PR? Check all that apply. This is **mandatory**!
 
-  - [ ] New API version. (Such PR should have been generated with [OpenAPI Hub](https://aka.ms/openapihub)).
+  - [ ] New API version. (If API spec is not defined in TypeSpec, the PR should have been generated using [OpenAPI Hub](https://aka.ms/openapihub)).
   - [ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
   - [ ] Update existing version to fix swagger quality issues in S360.
   - [ ] Other, please clarify:

CONTRIBUTING.md

@@ -58,14 +58,11 @@ See the [README.md](./README.md) for a description of the directory structure to
 
 If you want to contribute to the repository, follow these steps:
   1. Fork the repository and create a new branch for your changes.
-  2. If you are introducing a new api-version, create a new directory for that api-version and copy all the files from the previous version into the new directory. Make this the very first commit in your branch and then make your changes in subsequent commits.
-  3. Use the [linting tools](#coding-style) to check your changes for compliance with the OpenAPI v2 standard, the Azure REST API Guidelines and that Azure API Style Guide.
-  4. Push the changes to the branch in your fork until the branch is ready to be integrated.
-  5. Rebase your branch if needed to incorporate any changes to **main** and submit a pull request to the **main** branch using either the "control plane" or "data plane" PR template -- the main PR template lets you select which one.
-  5. Resolve any issues flagged by the [Pull Request checks](#pull-request-checks).
-  6. Contact the ARM API Review board or Azure API Stewardship team to request PR review. 
-
-Microsoft employees can use [OpenAPI Hub](https://aka.ms/openapihub) for adding a new API version.
+  2. Push the changes to the branch in your fork until the branch is ready to be integrated.
+  3. Rebase your branch if needed to incorporate any changes to **main** and submit a pull request to the **main** branch using either the "control plane" or "data plane" PR template -- the main PR template lets you select which one.
+  4. Resolve any issues flagged by the [Pull Request checks](#pull-request-checks).
+
+**Note:** Microsoft employees can use tooling for adding a new API version available [here](https://eng.ms/docs/products/azure-developer-experience/design/api-specs/api-specs), specially if not working with TypeSpec.
 
 ## Pull Request Checks