remove capability check

[bcwu]

Intent

This PR removes the server capability check in order to allow Python for Shiny to be deployed with a base Connect license.

The other reason for the functionality removal is that the functionality it is redundant. Connect itself will return the corresponding error messages if the server does not have APIs enabled or if Python is not enabled. Maintaining this check client side check is not only redundant, but actively obstructs server features from being functional without a client side change.

Type of Change

• Bug Fix
• New Feature
• Breaking Change

Approach

Automated Tests

Directions for Reviewers

Checklist

• I have updated CHANGELOG.md to cover notable changes.
• I have updated all related GitHub issues to reflect their current state.

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
4169	2638	63%	0%	🟢

New Files

No new covered files...

Modified Files

File	Coverage	Status
rsconnect/actions.py	33%	🟢
rsconnect/api.py	66%	🟢
rsconnect/bundle.py	77%	🟢
rsconnect/main.py	54%	🟢
TOTAL	57%	🟢

updated for commit: 11617c4 by action🐍

[kgartland-rstudio]

Validating all "api" content is still undeployable. The only content type that should be deployable is Jupyter notebook.

Testing with Python APIs disabled:
proper error:

This content is not authorized to be deployed on this server (deployment-unauthorized-error)
Error from Connect server: API applications are not permitted by your license.
Error: Task exited with status 65.

Can't deploy

• flaskapi
• fastapi
• dash
• streamlit
• bokeh
• shiny
• Voila notebook

no error:
Can deploy

• Jupyter notebook

via Jupyter UI

• Jupyter notebook

Testing with Python APIs enabled, all Content deploys.