multiple changes: mainly improve SecOC support and Container-PDU support

[tainnok]

I have made a couple of changes to address issues a faced during loading/using different real-world arxml-files.
(i am using canmatrix < 1.0 since several years and made some adaptions to add features. now as i do the migration to canmatrix >= 1.2 i decided to bring back most of my adaptions).

I tired to split my changes into several pull-requests so that you can review the changes by it's topic.
But as changes depends on each other it is not possible (at least for me in a manageable amount of time) to create seperated pull-request without facing the problem of merge-conflicts.

So i added this pull-request which contains all the changes (but the other pull-request still exist as 'draft', if you are interested you can investigate that pull-requests to see roughly the changes involved for the specific topic).
i hope that is okay for you :)

I use this changes with arxml-files created by differend manufacturers which are using different styles/features of arxml.
e.g. Container-PDUs with Header, Container-PDU without Header, SecOC-Messages, SecOC-Messages inside Container-PDUs (with and without Header), using SecOC of type "cryptographic" (special kind of secoc), using Autosar-Base-Platform-Types and different kind of Signal definitions.

fyi: my use-case it to load files (arxml and dbc) using the load() method and working with the returned objects.
Beside using the extracted informations i also use the decode/encode of canmatrix.

For more details see the individual pull-requests:
#864 improve generated signal for the 'updatebit'
#865 e2e add data_id_mode, prevent exception if PROFILE-NAME is not present
#866 add support for container-pdus without sub-pdu Header
#867 add support for AutosarBasePlatformTypes
#868 improve secoc-support, add support for type 'cryptographic', add support if secoc-msg inside container-pdu, get/extract more mandatory secoc-informations
#869 fix: do not generate invalid initial_values for Signals
#870 fix wrong frame-attributes because of frame-cache
#871 add comment for wrong behavior, change logging-level

i hope this 'cumulative' merge-request (with details in the listed draft-pr) is okay for you :)

[ebroecker]

Hi @tainnok

thanks a lot for all your prs!

Please give me some time to find enough time to have a real look on it.
Currently I am on holiday, so it could take some time till I'll merge....

Thanks again