Spotify Electron v2.0 & AWS services revoked access

[AntonioMrtz]

Access to AWS Services Subscription was revoked by Universidad de Murcia(UMU). This means STREAMING_SERVERLESS architecture is no longer supported in production.

Before this event, a new streaming architecture that does not use AWS services was planned for release in v2.0. We will reduce the content for the v2.0 release and accelerate its development and production deployment.

In order to overcome this situation we plan to:

• Implement streaming song service without AWS services
• Disable unsuported AWS Architecture pipelines
• Set architecture as deprecated in docs and set new default architecture. Readme and Mkdocs
• Update all docs
• Create new discussion to inform community
• Clean trello tasks like "Improving lambda arch"
• Spotify Electron v2.0 release roadmap
• Create a release procedure for new versions
• Cloud Deployment in Render for v2.0

Roadmap of this release version tasks will be updated at the trello card for Spotify Electron v2.0 release.

All help is appreciated :)

Release related tasks:

• Check Docs Spelling and Consistency #199
• Deprecate AWS Architecture #220
• STREAMING_BLOB architecture using streaming #222
• Release procedure docs #224
• Package app for Linux and Mac #225
• Remove duplicate assets for docs and readme #231
• Add playlist to playlist overwrites content #235
• Frontend debug Electron + React #237
• Only allow audio files for song uploading #239
• Calculated field/property for artists total streams #227
• Enable missing auth on new endpoints #242
• Build backend use prebuilt enviroments #244