Are TLS 1.2 AES-CBC and AES-GCM Authenticated Encryption ciphersuites? In the answer of the following post: Why was AES CBC removed in TLS 1.3?, I quote the following from the chosen answer:


  After the Lucky13 attack (a timing oracle caused by MAC-then-encrypt),
  it was thought that TLS should change ordering of the operations.
  Changing order of the operations would have affected the backwards
  compatibility with previous implementations so it was after all
  thought that it is more practical to switch to authenticated
  encryption only.


In the answer, it is assumed that AES-CBC in TLS 1.2 is not Authenticated Encryption (reference to the last part of the quote: it is more practical to switch to authenticated encryption only. 

My questions: 


When can I consider a ciphersuite an Authenticated Encryption? 
Is AES-CBC in TLS 1.2 an Authenticated Encryption (it uses MAC-then-Encrypt construction). 
Do padding attacks in AES-CBC render it considered non-Authenticated Encryption cipher?
When can I consider a ciphersuite an Authenticated Encryption?


To cite from Wikipedia: Authenticated Encryption:


  Authenticated encryption  ... is a form of encryption which simultaneously provides confidentiality, integrity, and authenticity assurances on the data.


Note the focus on simultaneously.


  Is AES-CBC in TLS 1.2 an Authenticated Encryption (it uses MAC-then-Encrypt construction).


Since the authentication tag in the form of MAC is added before and not during encryption it can not be considered authenticated encryption. This allows the padding oracle attacks because this means that the authentication tag can only be verified after decryption.