[BUG] SentEvent object does not contain RenderedSubject

[tmorenovasquez]

Describe the bug
After pulling a SentEvent object, I don't see rendered subject anywhere in the object even though the SFMC API docs mention Sentevent should contain rendered subject https://developer.salesforce.com/docs/atlas.en-us.noversion.mc-apis.meta/mc-apis/sentevent.htm

To Reproduce

import FuelSDK
stubObj = FuelSDK.ET_Client(params=params) 
get_sent_events = FuelSDK.ET_SentEvent() 
get_sent_events.auth_stub = stubObj 
get_sent_events.search_filter = {'Property' : 'SendID','SimpleOperator' : 'equals','Value' : id} 
sent_events = get_sent_events.get() 
for send in sent_events.results: 
    print(send)

Which gives me an object like

 (SentEvent){
    Client =
       (ClientID){
          ID = 526003768
       }
    PartnerKey = None
    PartnerProperties[] =
       (APIProperty){
          Name = "ListID"
          Value = "90"
       },
       (APIProperty){
          Name = "SubscriberID"
          Value = "3183704"
       },
    ObjectID = None
    SendID = 5497
    SubscriberKey = "test@test.com"
    EventDate = 2021-11-01 08:30:39.913000
    EventType = "Sent"
    TriggeredSendDefinitionObjectID = None
    BatchID = 1
  }

Without the rendered subject

Expected behavior
I expected RenderedSubject to be a key in the object

Code snippet
A code snippet that demonstrates the issue or a link to a code repository the developers can easily pull down to recreate the issue locally.

Note: Because the developers need to copy and paste the code snippet, including a code snippet as a media file (e.g. gif) is not sufficient.

Environment

• Salesforce-FuelSDK 1.3.0
• Python 3.8.10

The bug has the severity

• Critical: The defect affects critical functionality or critical data. It does not have a workaround.
• Major: The defect affects major functionality or major data. It has a workaround but is not obvious and is difficult.
• Minor: The defect affects minor functionality or non-critical data. It has an easy workaround.
• Trivial: The defect does not affect functionality or data. It does not even need a workaround. It does not impact productivity or efficiency. It is merely an inconvenience.