Update PAPI component, should cause a new build

[AlexTugarev]

Description

Motivation is to force a new build of PAPI component.

Summary generated by Copilot

🤖 Generated by Copilot at a4f6bd5

This pull request removes the Roadmap section from the Usage section of the components/public-api-server/README.md file. This simplifies the documentation and avoids duplication of the public API server roadmap.

Related Issue(s)

Fixes #

How to test

Documentation

Preview status

gitpod:summary

Build Options

Build

• /werft with-werft
  Run the build with werft instead of GHA
• leeway-no-cache
• /werft no-test
  Run Leeway with --dont-test

Publish

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer

• analytics=segment
• with-dedicated-emulation
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment / Integration Tests

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh. If enabled, with-preview and with-large-vm will be enabled.
• with-monitoring

/hold

[AlexTugarev]

@akosyakov could you ✅ , please?

[AlexTugarev]

/unhold