Fixed an NPE when parsing malformed subjects

[bashir2]

Description of what I changed

See the added unit-test for an example malformed subject that triggers this.

E2E test

TESTED:

Added unit-test to reproduce the reported issue.

Checklist: I completed these to help reviewers :)

• I have read and will follow the review process.

• I am familiar with Google Style Guides for the language I have coded in.

  No? Please take some time and review Java and Python style guides.

• My IDE is configured to follow the Google code styles.

  No? Unsure? -> configure your IDE.

• I have added tests to cover my changes. (If you refactored existing code that was well tested you do not have to add tests)

• I ran mvn clean package right before creating this pull request and added all formatting changes to my commit.

• All new and existing tests passed.

• My pull request is based on the latest changes of the master branch.

  No? Unsure? -> execute command git pull --rebase upstream master

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 71.42857% with 2 lines in your changes missing coverage. Please review.

Project coverage is 50.74%. Comparing base (c2356c8) to head (759da3c).

Files with missing lines	Patch %	Lines
...java/com/google/fhir/analytics/FetchResources.java	71.42%	0 Missing and 2 partials ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##             master    #1291      +/-   ##
============================================
- Coverage     50.76%   50.74%   -0.03%     
- Complexity      692      693       +1     
============================================
  Files            90       90              
  Lines          5726     5725       -1     
  Branches        775      776       +1     
============================================
- Hits           2907     2905       -2     
- Misses         2533     2535       +2     
+ Partials        286      285       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[chandrashekar-s]

Thanks @bashir2 for fixing this bug.

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.