Fix #1279, rtems queue multi-size, mimic posix logic

[thesamprice]

Checklist (Please check before submitting)

• I reviewed the Contributing Guide.
• I signed and emailed the appropriate Contributor License Agreement to [email protected] and copied [email protected].

Describe the contribution
Refactor rtems queue to not do size check, and to mimic posix logic.

Fixes #1279

Testing performed
Steps taken to test the contribution:

1. Build steps '...'
2. Execution steps '...'

Expected behavior changes
A clear and concise description of how this contribution will change behavior and level of impact.

• API Change: xxx (if applicable)
• Behavior Change: xxx (if applicable)
• Or no impact to behavior

System(s) tested on

• Hardware: [e.g. PC, SP0, MCP750]
• OS: [e.g. Ubuntu 18.04, RTEMS 4.11, VxWorks 6.9]
• Versions: [e.g. cFE 6.6, OSAL 4.2, PSP 1.3 for mcp750, any related apps or tools]

Additional context
Add any other context about the contribution here.

Third party code
If included, identify any third party code and provide text file of license

Contributor Info - All information REQUIRED for consideration of pull request
Full name and company/organization/center of all contributors ("Personal" if individual work)

• Note CLAs apply to only software contributions.

[thesamprice]

The posix diff vs rtems diff
This is a more aggressive change than just deleting the size check.

[skliper]

Looks great! Probably should use OSAL_SIZE_C to explicitly convert to size_t, I think that would avoid implicit conversion warnings if/when we ever do that analysis. Looks like you'll need to run clang-format-10 (or fix formatting by hand) to squash the format workflow error.

[chillfig]

@thesamprice, would you please take a look at the unit test failure before merging?

[thesamprice]

@jphickey You recently added fix-1252-condvar-api. Is there anything in this merge that would be causing that test to fail?

[thesamprice]

@chillfig Not sure why the last update fixed the unit test failure, but i guess adding OSAL_SIZE_C casting fixed it?