Publish to NPM instead of custom feed

[edvilme]

The PythonEnvironmentsAPI is intended to allow other people's codes to communicate with this extensions to leverage its functionality. This includes for example, several Python VSCode Extensions. Hence, it should be easily available to all via the npmjs.com registry.

===========

This pull request updates the build and publishing pipeline for the npm package, primarily to reflect the renaming of the package directory from pythonEnvironmentsApi to api and to simplify the publishing process. The changes also streamline the pipeline by removing legacy steps and variables related to Azure Artifacts and the msft_consumption feed, and by updating the publishing mechanism to use a new template.

Key updates include:

Pipeline directory and variable updates:

• All references to the package directory have been updated from pythonEnvironmentsApi to api in the pipeline configuration and variables, ensuring consistency with the new directory structure. [1] [2]
• The homepage field in api/package.json is updated to point to the new api directory.

Pipeline simplification and publishing changes:

• The pipeline template now uses MicroBuild.1ES.Official.Publish.yml instead of the previous template, and the build steps for installing dependencies, compiling, and packaging have been inlined instead of being parameterized. [1] [2]
• The stages and jobs related to publishing to Azure Artifacts and the msft_consumption feed, including managed identity authentication and custom .npmrc creation, have been removed. Instead, publishing now uses a standardized MicroBuild template for npm package distribution.

These changes help modernize and simplify the build and release process for the npm package.