chore: CRP-2694 delete encrypted notes dapp (#1231)

Author: altkdf

.github/CODEOWNERS

@@ -22,7 +22,6 @@
 /motoko/counter/ @dfinity/languages
 /motoko/daily_planner/ @dfinity/ninja-devs
 /motoko/encrypted-notes-dapp-vetkd/ @dfinity/crypto-team
-/motoko/encrypted-notes-dapp/ @dfinity/crypto-team
 /motoko/evm_block_explorer/ @dfinity/ninja-devs
 /motoko/filevault/ @dfinity/ninja-devs
 /motoko/flying_ninja/ @dfinity/ninja-devs
@@ -65,7 +64,6 @@
 /rust/counter/ @dfinity/growth
 /rust/daily_planner/ @dfinity/ninja-devs
 /rust/encrypted-notes-dapp-vetkd/ @dfinity/crypto-team
-/rust/encrypted-notes-dapp/ @dfinity/crypto-team
 /rust/evm_block_explorer/ @dfinity/ninja-devs
 /rust/face-recognition/ @dfinity/execution
 /rust/flying_ninja/ @dfinity/ninja-devs

.github/workflows/motoko-encrypted-notes-example.yml

@@ -1,15 +1,13 @@
 # Encrypted notes: vetKD
 
-This is a copy of the `encrypted-notes-dapp` example, adapted to use [the proposed vetKD feature](https://github.com/dfinity/interface-spec/pull/158) and add sharing of notes between users.
+Encrypted notes is an example dapp for authoring and storing confidential information on the Internet Computer (ICP) in the form of short pieces of text. Users can create and access their notes via any number of automatically synchronized devices authenticated via Internet Identity (II). Notes are stored confidentially using vetKeys. The end-to-end encryption is performed by the dapp’s frontend.
 
-In particular, instead of creating a principal-specific AES key and syncing it across devices (using device-specific RSA keys), the notes are encrypted with an AES key that is derived (directly in the browser) from a note-ID-specific vetKey obtained from the backend canister (in encrypted form, using an ephemeral transport key), which itself obtains it from the vetKD system API. This way, there is no need for any device management in the dapp, plus sharing of notes becomes possible.
+In particular, the notes are encrypted with an AES key that is derived (directly in the browser) from a note-ID-specific vetKey obtained from the backend canister (in encrypted form, using an ephemeral transport key), which itself obtains it from the vetKD system API. This way, there is no need for any device management in the dapp, plus sharing of notes becomes possible.
 
 The vetKey used to encrypt and decrypt a note is note-ID-specific (and not, for example, principal-specific) to enable the sharing of notes between users. The derived AES keys are stored as non-extractable CryptoKeys in an IndexedDB in the browser for efficiency so that their respective vetKey only has to be fetched from the server once. To improve the security even further, the vetKeys' derivation information could be adapted to include a (numeric) epoch that advances each time the list of users with which the note is shared is changed.
 
 Currently, the only way to use this dapp is via manual local deployment (see below).
 
-Please also see the [README of the original encrypted-notes-dapp](../encrypted-notes-dapp/README.md) for further details.
-
 ## Prerequisites
 
 This example requires an installation of: