Create Feature Compliance Manifest for ably-python

[QuintinWillison]

For motivation, see Future Direction for the SDK Manifests.

Acceptance criteria:

Scope of work under this issue:

• the manifest should have a conformed name and location, as decided in the work done under Define and document standard filename and location for feature manifest files in SDK repositories features#6
• A CI check must be added that uses our new GitHub Action, validating and render SDK manifests against the canonical features list (see internal Jira story SDK-2403)
• A CI step must be added that pushes the rendered manifest view to sdk.ably.com using our SDK Upload Action

[QuintinWillison]

To explain my addition of a suffix to this issue's title, despite its superfluous nature given the GitHub context, it helps us internally when viewing this issue under the Jira epic that it's sync'd to internally. Sorry.

[QuintinWillison]

The manifest was created in ably/features#79, which will close this issue, because the remainder of the scope of work outlined in the opening commentary for this issue duplicates much of what's described in SDK-2403 (internal). Moving the manifest to this repository will be handled under that story.